[virtualeyes]

Twitter did not think Rails was particularly adequate at serving up anything (for their extreme needs), so they dumped it for the JVM.

Charles Nutter is doing genius work with JRuby, btw, that's where Ruby has a future with the enterprise, on the JVM. Twitter dumping Rails for Scala was a major win for Odersky & friends, and a big hit to Rails (though Ruby/Rails continues to innovate, nothing has changed there)

Not sure why client-side applications take a second or 2 to render a page, but if that is the case, cached html on front end server would be dee way 2 go, just avoid hitting the application server entirely...

[n8agrin]

Twitter didn't dump Rails, or Ruby.

[virtualeyes]

Yes, you're correct, it was not an either-or proposition, I'm sorry, they dropped them both.

Seriously, I'm curious, what public facing, or any facing, components does Twitter use that is written in Ruby and/or Rails?

A Google search for "twitter rails" brings up the usual got dumped threads. A similar search, but this time, "twitter scala" brings up, as a first result "Scala School" for Twitter engineers, followed by a bunch of threads on the Twitter + Scala marriage.

Don't worry, Scala has its own issues (Yammer, for example, ditched Scala for Java due to, ironically enough, scalability issues).

[getsat]

I have multiple friends working at Twitter. The frontend is still all Rails.