On the plus side, RoR is going to gain a lot from this: a better plugin architecture and with a bit of luck some performance gain. It will also regroup a lot of the Ruby expertise under one roof.

That being said, how long before we see a fork from people who wants to keep MERB “pure” ?

thanks, that makes sense. i’m not familiar with this community, got here by a link. thanks again!

What was the point of your introductory sentence? The one where you apologized to everyone that isn’t a Rubyist? Do you prefix all your articles with an apology to all the technologies not covered in said article? That’s a little weird.

As part of the work we did on Merb, we also looked and learned a lot from other frameworks (inside and outside of the ruby world, Django being a good example). We will continue to do that and to be inspired by the numerous awesome projects out there.

People also need to realize that the merb team will also bring along a different world view. Merging two great teams with slightly different approaches will enrich the project more than anyone can expect.

People who judged Rails and the Rails team few years ago might want to reconsider. This move from the Rails team is a significant gesture showing that they are not stuck in their ways and want the best for the community.

Hopefully some of you readers, will give Rails 3.0 a go and will find something they will want to adopt.