On Dec 23, 2008, at 9:48 pm, Will Jessop wrote:
> You have probably heard from twitter now, but Ruby on Rails and Merb > are merging: > > http://brainspl.at/articles/2008/12/23/merb-is-rails > http://rubyonrails.org/merb > http://yehudakatz.com/2008/12/23/rails-and-merb-merge/ > > What do people thing, will we get an amazing framework, or will the > creation of a monoculture be a problem? > > I think the former, Rails was doing OK before Merb got big. =( The best thing about Merb was it wasn't run by DHH. I've had a few arguments about BDD strategies on the merb list, but beyond that I admire the Merb team's attitude to quality (external and internal). Notice how all the bullet points on Katz's post[1] are things Rails will get from Merb (I await DHH's version). Rails doesn't do much that Merb doesn't, but Merb is much better engineered, more library- agnostic, doesn't pollute the standard library, and violates POLS far less often than Rails. I suspect if they pull it off, the result will be more Merb 2 than Rails 3. Well it better be, or I'll be doing all my future apps in Ramaze :) Ashley [1] http://yehudakatz.com/2008/12/23/rails-and-merb-merge/ -- http://www.patchspace.co.uk/ http://aviewfromafar.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NWRUG" 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/nwrug-members?hl=en -~----------~----~----~----~------~----~------~--~---
