Merb is Rails
brainspl.at
brainspl.at
That said, the wording of things currently is unsettling. This happened because Merb is considered technically better, more sophisticated, and Rails has the backing and the momentum. They merge so that both have both. I have some qualms with the fact that Merb seems to be taking a back-seat in titles like Merb is being merged into Rails.
I worry that Merb will feel like Rails when it really should be the opposite. This has been mentioned in #merb and, again, Yehuda assures us we will be happy. I believe that, even though it's all a bit hard to digest.
Lots of us are skeptical, but it is very important that we support this. That way, any issues will be mitigated.
But that's the correct phrasing no matter what the underlying technical reality is. Rails is the established brand! People know what Rails is! Nobody but blog-reading Ruby programmers has any idea what Merb is!
Even if the plan was to throw all existing Rails code in the trash and have the Rails core team switch to Merb, they would still call the result "Rails". Throwing away the Rails brand would be insane, and diluting it by calling it "Rails/Merb" or "Mails" or something would likewise be insane.
I completely agree. It should keep the Rails name. That is not my point though. They will have to rewrite most of the core and probably use large portions of Merb, that is not merging Merb into Rails. It could be a merger of the two projects, or even rebranding Merb as Rails, but it's not that.