I think this is fantastic. Why you say? Because Rails has mindshare
and you can get paid to write it. Merb is better implementation,
learning from all the mistakes of Rails and from its own first
versions. People I hear talking about learning Merb usually do so
because they're tired of Rails, but Rails is what you can get paid for
now. So soon, in Rails 3, you will get all the benefits of Rails
mindshare, etc., except that you'll be writing Merb code. It's like
if Sun and Matz got together and decided that Java 7 would be Ruby
1.9. Wow, we could all go out and get those great paying Java gigs.
Ok, perhaps a bit of a stretch but you get the idea.
The only fear I have is that Merb will be bogged down by the legacy
requirements of Rails. How many sacrifices will be made in the name
of backwards compatibility or supporting certain large user bases? If
it's a clean API break, then I salute the Rails team for having balls
of steel.
David Koontz