Twitter didn't "drop Ruby". They just replaces (huge) parts of their stack by other things that might or might not written in their old default language. As wil

Twitter didn't "drop Ruby". They just replaces (huge) parts of their stack by other things that might or might not written in their old default language. As will anyone that has to work at their scale. Their frontend was still Rails for a long time (or still is, in parts?). Example: see what they have to offer as open source. Still quite a bit of Ruby: http://twitter.github.com http://twitter.github.com