I'm not sure that would have been a solution. Twitters problems are architectural, telecoms-scale ones. Rails is unlikely to ever be suited for problems like t

I'm not sure that would have been a solution. Twitters problems are architectural, telecoms-scale ones. Rails is unlikely to ever be suited for problems like that, and it feels like any attempt to make it so would neuter some of the benefits it offers elsewhere. On the other hand, PHP is just a language and doesn't enforce architectural style. A much better option for this sort of thing, IMO.