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
{{#tags}}- {{label}}
{{/tags}}