zlacker

I would use Rails, but I wouldn't do things like try to write an asynchronous message queue in Ruby (like Twitter did).

I mean sites like Shopify, Hulu, YellowPages.com, etc. "handle the strain" just fine.

>>phaedr+(OP)
How much of the content in those sites change as fast as Twitter does? Mainly static content can be displayed using about any framework/language. Moreso when you include caching. I don’t think Rails was simply a good choice for the workload Twitter needed to support (not that they knew it at the time).