Is that made in China, mh?

The issues Twitter has had with scaling are pretty famous, and it’s got NOTHING to do with Rails. The problems have all been with the DB (Twitter is an immensely demanding application database-wise, orders of magnitude greater than a simple blog like this) and the IM interface ejabberd, plus basic technical constraints like the messaging system. Add to that the clowns at Joyent and a severe lack of financial freedom and experienced people to hire, and you’ve got a recipe for disaster.

You really just don’t know what you’re talking about, and neither do your Rails devs with their “fingers on the pulse” (yeah, right). Blaine Cook is a highly competent guy and the fact he’s managed to keep Twitter mostly running is almost a miracle. I’d hire him in a millisecond.

This kind of worthless, wilfully ignorant, misleading BS is a key reason I don’t read TechCrunch and advise others to do likewise.

I’m pretty sure you’re not that dumb to think it’s a problem with Rails. Mainly because twitter’s jabber/SMS gateways stuff ( where they face scaling issues ) is definitely NOT in ruby/rails, but possibly in Erlang.

So, please, stop feeding idiotic trolls like Josh Stodola.

So the real question here is: Who is the fucktard who decided to go with (and stay with) Ruby on Rails?

Having watched a fair number of businesses over the years, it probably *is* appropriate to blame the board more than Mr. Cook, in the sense that once Twitter got a board and VC funding and became a business (a revenue-free business, but a business nonetheless), it became the board’s responsibility to say, “Hey, you built good stuff but you can’t build what we need to make it scale, so you’re mutually deciding with us that it’s time for you to leave. We’re going to give you this gold watch, a big paycheck and a plush doll of DHH that says ‘Fuck you!’ when you pull the string. Best of luck.”