It shouldn't be an all-or-nothing situation. There are obviously parts of Twitter that would work best as non-Rails. Ruby is too slow for certain things, and so you determine which of those certain things are in your application and you build them in C or Java.

For Twitter, I think some parts of the API need to be in C. But the whole service? I doubt it.