This post originated from an RSS feed registered with Ruby Buzz
by Andy Delcambre.
Original Post: Merb 2 == Rails 3
Feed Title: Andy Delcambre
Feed URL: http://feeds.feedburner.com/andydelcambre
Feed Description: Andy has been using Ruby and Ruby on Rails since 2006 and has been working with Ruby on Rails professionally since June 2007.
Unless you have been under a rock all day, I am sure you have heard about the Rails and Merb merger announced earlier. I am very excited about this turn of events. It seemed so incredibly improbable merely one week ago. The more I think about it and hear the plans, the more optimistic I become about the future of Ruby on the web.
You can read the details of the merger at Yehuda and David’s blogs. There is also coverage from Carl Lerche, Tom Mornini, Matt Aimonetti, and Ezra Zygmuntowicz. I am not going to speak to the technical aspects of the merger as David and Yehuda have outlined those plans thoroughly. I am more concerned about the community facets of the merger.
Assuming the technical issues can be worked out with the merging of ideas and code bases, this is absolutely fantastic news for the ruby community at large. There is huge mind share that rails has already garnered in the past four years. Merb has been gaining ground, but unfortunately primarily from the existing rails community. It has grown since it’s inception two years ago and has experimented with many new concepts and ideas that will find an excellent new home in Rails. There will be some stumbling blocks along the way. Almost assuredly more so for merb apps than rails apps, due primarily to the sheer volume of rails code out there, especially in comparison to merb. There will be migration paths from both frameworks to Rails 3.0 that should be fairly painless.
My biggest concern for the moment is people who are currently working on Merb applications. I know that the Merb core team has committed to making point releases leading up to the transition to Rails 3.0, but until we get there I worry that major forward progress on merb will stop (understandably so). This just leaves those of us working with current merb apps with a bit of an unmaintained framework for the moment. This will end up with everybody in a better place, but will leave things a bit painful for the moment.
Overall I am very excited for the coming months of ruby web development. It is so cool to see the communities come back together like this and truly allow us to get the best of both worlds. I am looking forward to what the new core team can come up with.
Previous Topic
