Rails 3.0: It's ready
Not to cry sour grapes here but there is not one mention of Merb in that entire blog post. I personally wrote merb in order to show that rails internals could be much better, modular and faster. I did heavy duty politicking to get the two teams to come together and I think the rails merb merger is one of the coolest open source success stories vie heard of.<p>But not a single mention of merb in this entire post. I'm not complaining but it seems disingenuous not to mention it as the sole reason I wrote merb was to push rails forward. And when it looked like merb might possibly overtake rails I went ahead and gave merb to the rails project and got the two teams together so there wasn't wasted effort. After all to have ruby and rails itself win we needed to compete with java and python and php. Merb was starting to fragment the ruby community as it became a more and more viable option and I did some personal heavy politicking to get it merged back into rails so we could take on the world instead of infighting within the ruby community.<p>I think it's been a great success story and most of the ideas of merb's architecture have made it into rails.<p>So I'm incredibly happy to see rails 3 finally come out. And I'm incredibly happy that my little experiment in making rails architecture better has paid off and the two projects merged. But I do think it's a bit weak that merb was not mentioned once in the article.<p>(Edit) all this being said I don't want to come across as co plaining. My work on merb ended up exactly as I wanted it to, it made rails better.<p>So huge congratulations to the rails team for making this happen!<p>(Edit) <a href="http://rubyonrails.org/merb" rel="nofollow">http://rubyonrails.org/merb</a>