What a great read. I dropped Rails five years ago, and hadn't really caught up on what happened with it (just heard the rumors). Reading about the whole Merb/R

What a great read. I dropped Rails five years ago, and hadn't really caught up on what happened with it (just heard the rumors). Reading about the whole Merb/Rails 3 debacle was a huge deja vu experience. I come from the SproutCore world, and somehow we ended up with the author of Merb running our project (despite NO previous experience with either SproutCore or application frameworks in general). Anyway, long story short, I think this quote about sums up what happened with SproutCore: > Going back to the larger issue, Rails definitely went off the rails. Cleaner, more modular APIs are an important goal, but they're way less important than speedy development, a modern feature set -- why is Rails not staying up to date with HTML5 the way it did with Ajax? -- and, above all else, programmer happiness. The Merb integration rewrite was a giant, time-wasting threadjack with only a few small payoffs, and DHH, who wrote two whole books about why you should turn down feature requests, should have nixed the whole thing. I'm still not sure that SproutCore will recover from the damage, which has been extensive (unlike Rails, which actually did release Rails 3, "SproutCore 2" has been completely abandoned, and the changes made to SproutCore 1 to support SproutCore 2 have caused huge problems).