Couple points: - Merb name doesn't make all that much sense anymore. Mongrel + Erb? Anyone still use mongrel? Rails is a good name, despite the technology baggage.
- Rails has amazing industry adoption for such a offbeat Ruby framework. Books + IDEs + consulting are huge for a project that a young Danish punk put together in his spare time. Pretty good reason to - I'm extremely excited about this news. Having a small niche framework is fun for a while, but not so much when you have no one to write patches+documentation, and constantly find bugs in stuff that you really expected to work. Having a larger user base and ecosystem is always better than not. My only concern is compromises. I do believe rSpec will win out as I think even test::unit users agree its a better organized framework. I'm hoping that they handle Rails 2.x compatibility via a plugin, and not keep supporting the dead weight features that Merb provides superior approaches to. My 5 biggest frustrations with Rails are: - render / redirect spaghetti code. each controller action should return a string - concat and erb buffers. every view helper (including ones that take blocks) should return a string - _url routes. unified url generation is vastly superior. helpers should use strings - rails gem plugins. these need to be deleted and replaced by Merb's superb new dependency management - no good pluggable apps solution (embraced engines for many months. it was a bad many months) The reason I switched to Merb for all new project development is that it addressed all these with really slick solutions. As long as most of these issues get addressed in Rails 3.0 (which I plan on wholeheartedly contributing to), I wont have any problems and the additional benefits of the merge will pay off (bigger less fragmented community, better documentation, more jobs, etc). Really looking forward to the Roadmap. This is a big issue that will impact the future of many Merb developers who are currently working on projects/plugins/patches that now may be disposable. The more open the transition, and the earlier the roadmap, the better. Thanks! On Dec 23, 7:03 pm, Justin Reagor <[email protected]> wrote: > > Bigger community? > > Better documentation? > > Wider industry adoption? > > PS I use rails at work and merb at home. I don't have anything > > personal against rails. Just sad to lose a choice. My bet is merb > > will eventually resurrect itself sometime before or after Rails 3.0. > > Your points are dead on in my book... with a dash of "WTF I smell > fish?". Can you imagine what Merb would be on its own by the time > Rails 3.0.x is perfected? > > I also can't see other frameworks like SproutCore, adopting Rails. > Unless Rails 2 is trashed and completely replaced by Merb. In which > case, why does Rails get the title and tech just handed to it? Because > we need the logo rights? > > :: Justin Reagor > :: [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
