Maybe you (commenters and new viewers) should look into why they were having scaling issues in the first place and what Twitter themselves have to say about it:

Blaine Cook, Twitter’s lead architect, held Ruby blameless:

“For us, it’s really about scaling horizontally – to that end, Rails and Ruby haven’t been stumbling blocks, compared to any other language or framework. The performance boosts associated with a “faster” language would give us a 10-20% improvement, but thanks to architectural changes that Ruby and Rails happily accommodated, Twitter is 10000% faster than it was in January.”

- source: http://highscal...-percent-faster

Ruby on Rails is a great, great framework – comin from the mouth of a long time PHP Developer. I highly recommend looking in to the latest releases of Ruby on Rails, any questions of scaling issues are mute now since Ruby on Rails was young, they have since then been resolved and excelling.

I hope you don’t read a year old post and take it as truth and give up on Ruby on Rails – take note on how fast technology progresses and be sure to read newer / more recent blog posts.

Great article though – at the time

That said, Ruby and Rails are not only beautiful syntactically, but are enormously functional, and as a long-time PHP programmer I recognize that I can develop web apps 2-5 times more quickly on rails, but don’t sacrifice any of the flexibility that comes with building an app without a framework. Not only that, but because Ruby organizes everything in classes, and Rails organizes everything into the MVC design pattern, my applications are boundlessly more accessible and easy to maintain, especially late in the development cycle.

Example? I need to change XML conifguration in Rails so that output files don’t convert underscores to dashes, because Adobe Flex (MXML) can’t detect assignments to hyphenated XML elements. In PHP, it’s a snap to change XML output so that Flex apps written in MXML compile without problems. In Rails? It can likely be done, but the point is that it is _damned hard to find out how_. Sure, I can write my own. But why should I have to? This sort of thing comes up a LOT as soon as one tries to do something beyond the Very Tired shopping cart app.

The fact is that not only can one find plenty of support for such problems in PHP, but one can also find plenty of PHP coders to do the work. Even if I develop something cool for a client in Rails, how can I sell them on the idea that they will be able to find competent support when I am gone?

Rails is not ready yet. In fact, it might never be, and any professional developer will tell you as much.

http://www.ruby50.com