Along with the expansion in ambition came the fact that Merb and Rails started sharing more and more of the same ideas and even implementation. This led to a fair amount of unnecessary duplication on both sides of the fence and led to some paradox of choice. When do I choose one over the other and when?
On December 23rd, we decided to end the duplication and the paradox of choice. That was the day we declared our intentions of bringing the best ideas of Merb into Rails 3. That was the day we announced our commitment to work together.
The Rails team and the Rails community offers their warmest welcome to the Merb team and the Merb community. We'd especially like to thank the key Merb people who'll be co-starring the effort to bring the bright Merb ideas in Rails: