Indeed, which is no doubt why Twitter is still using Rails. The sad thing is that there is an interesting tech story in this recent change in the Twitter Searc

Indeed, which is no doubt why Twitter is still using Rails. The sad thing is that there is an interesting tech story in this recent change in the Twitter Search architecture - "large company moves from synchronous web framework to asynchronous I/O and workflow framework" - but it's getting no discussion, because everyone is misreading Twitter's blog post as another chapter in the "Rails doesn't scale" non-story. There are interesting discussions to be had about language beauty and performance, but this story is not part of them. (Indeed the closest the Twitter post comes to discussing beauty is saying how their old Rails codebase was full of technical debt.) Read the original blog post [1] on the Twitter engineering blog - which the author of this article clearly didn't - for the real story, which is not about language wars, but about scaling a non-traditional web app. [1] http://engineering.twitter.com/2011/04/twitter-search-is-now-3x-faster_1656.html http://engineering.twitter.com/2011/04/twitter-search-is-now...