I seriously doubt they are actually going to rewrite Twitter in another language. That's a pretty dumb statement and prediction, and Michael Arrington just lost another notch of respect from me (he lost the previous one for his vicious attacks on that Blaine dude who archtected Twitter).
Sounds to me like Mr Arrington has an axe to grind and is putting that ahead of objective journalism.
I assume the difficulty is storing the data and then retrieving the right data when generating a page. Yeah, you can use a SQL database, but that doesn't seem to be working very well. So they probably need to write some custom storage backend that is actually designed for the load that is put on it. Relational databases are general solutions. General solutions are good for general problems, but not necessarily specific problems.
Anyway, if the problem happens to be that the Rails frontend is too slow, speeding that up isn't going to buy them anything long-term. Eventually the database is going to bog them down even if the web GUI is hand-optimized assembly.
JMHO, obviously I have no idea what the twitter codebase looks like or what specific problems they are having. I also don't use Ruby or Rails, but I doubt that's their problem.
That's the theory. Sometimes the practice isn't so simple, when you have 32423432234 lines of spaghetti code, all tangled up. Surely twitter isn't that bad, but I've been in situations where someone cited that very idea and it just wasn't feasible.
Unless you have massive engineering resources that's not dedicated to feature enhancements and new developments of your main product (ie. a small startup environment), a full rewrite is just too expensive.
Sounds to me like Mr Arrington has an axe to grind and is putting that ahead of objective journalism.
Daniel