Are you aware that Rails 3.0 supersedes Merb. If you want less options go with Rails. If you want tiny go with Sinatra or merb-gen very-flat
Pick the tool for the job - Merb works great as is. Has a lot of functionality and flexibility. Merb can be molded and manipulated to do what you want to do. I refuse to use Merb via gem install merb as you get a crap load of gems (as you have pointed out) and so use the bundler :) Nick On Wed, Nov 4, 2009 at 6:50 AM, DAddYE <[email protected]> wrote: > > Hi guys, > > I want to propose a little refactoring of merb. > > Now at the first view Merb for new guys same to be a little > complicated and with a lot lot lot lot gems, I like so much gems, but > 20+ gems when I do a fresh install of merb is a little strange. > > Im very interested in using merb sponsor it. As I say through pm with > the merb staff my society have a big experience with ruby framework > and personally I made some like 100+ websites/webapps. > > So, for me is necessary focus to some points: > > 1) Make merb more coincise (was born with some django philosophy... > but now?) > 2) Make merb a little smaller (in terms of gems) > 3) Make merb more stable but revolutionary > > 1) More Coincise: > > Now in merb for do one thing we have a lot of way for do that, I love > extensibility but for me I necessary (at the moment) have a one/two > way for do a thing, then if a developper want can easily extend it. > > Some examples of question of friends that tell me: > > Why merb-gen stack / core ? > Why merb-gen flat / very flat ? > > Why we can't simply have merb-gen app and merb-gen tiny-app ? Two > coincise way ... and a developper can easly extend it. > > Why we have gems for merb-actions-args? Why is not in the core? > > For example personally I forgotten that merb-action-args is > incompatible with ruby 1.9, so why confuse a lot of us (not all) with > them? > > Why merb-params-protections? Why is not in the core? At the moment I > don't remember the answer > > 2) Make merb a little smaller (in terms of gems): > > Now we have a gem for everything. merb-exceptions (that I love) merb- > assets merb-actions-args merb-slices etc... > > My pruppose is: > > - drop merb-actions-args > - merge with core merb-params-protections or drop it if not possible > - merge merb-assets with merb-helpers > - separate (at the moment) merb-exceptions > - drop merb-slices (I will explain why) > > There also another reason in this way the merb team can focus to > important things for people that use merb for big apps **productions** > envs. > > 3) Make merb more stable but revolutionary > > As I say now (for me) is the moment to focus for use merb in > production. A slogan is necessary few things that work well! > > Then, is time to give some thing new to the ruby scene, as Sinatra do. > > Merb now can't be a "mirror" of rails but a new framework. > > For example, merb-slices, some love it some don't love it, personally > I hate it, not because I don't apreciate it but because I very very > very complicated read the code written from antother person. Slices > like rails-engines are not linear. Why we can "duplicate" a thing that > just exist and we don't try to create a new way? > > I love one thing of django, the multiapp support. > > I dream but for me a thing like that will be beautiful: > > $ merb-gen project store > $ cd store > $ merb-gen app core > $ merb-gen app frontend-ecommerce-1 > $ merb-gen app frontend-ecommerce-2 > $ merb-gen app frontend-ecommerce-3 > > Then our dir can be like this: http://gist.github.com/225365 > > We can also made a routing like sinatra + sinatra-map that can be > "innovative" > > Other things in my opinion is very important to discuss: > > - Add a I18n (for example 30% of our sites use it) > - Use DM as default? There are big big project (like twitter) that use > it? Is stable? > > > At the end for me is necessary big refactoring so all of us can focus > to the **very important things** and use check test stress the "core" > services of merb. > > DAddYE > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
