Ruby and the MRI to lots-of-stuff and the JVM - mehack

i gave a talk at OSCON this year specifically about twitter's slow move from ruby (both the language, and the MRI) and rails to JVM-native technologies - its a follow on presentation from @evan's interview with infoq. there are a few top level reasons why we're making this move: great support for server workloads - as you can imagine, twitter is under immense load (we're one of the largest sites o

[yyamano]

[Jaav

[hfu]

「ruby will always be part of our infrastructure. i'm personally interested to see where the JRuby community is going to go with a performant Java 7 implementation.」

[SavingThrow]

"The big issue is that the performance impact of moving to JRuby is bound up in the quality of the various clients that you rely on. ... our memcached client for CRuby is extremely fast. JRuby clients, as far as my understanding goes, are not even within an order of magnitude as performant. "

[passingloop]

Twitter needs a real concurrency model