Re: Twitter on Scala
Posted: Apr 3, 2009 4:13 PM
> I find it remarkable that there's not a single mention of
> JRuby anywhere in this entire interview. JRuby brings at
> least some of the JVM characteristics they praise (better
> GC, built for long-lived processes, native threading) but
> remains Ruby. Plus JRuby has much-improved performance
> over the standard implementation. The JRuby team were
> never approached by anyone from Twitter about helping with
> their scaling issues. It seems like it would have at least
> warranted some exploration, and as far as I know, that
> never happened.
> I don't claim that JRuby could have solved all their
> scaling issues, nor do I expect JRuby will ever perform as
> well as Scala. But they talk about Ruby and the JVM as if
> they're mutually exclusive. That's obviously not true.
Yes, you're absolutely right. That question was on the tip of my tongue when I asked about the Ruby problems. I.e., I asked "Can you elaborate on what you felt the Ruby language lacked in the area of reliable, high performance code?" The reason JRuby popped into my head is that a lot of what they wanted to solve was solved by switching from the Ruby runtime to the JVM, not the Ruby language to the Scala language. And JRuby would have given them all that as well. But then I felt they kind of answered it. They said they missed static typing. So I moved on and didn't ask about JRuby. But it is a good question I should have asked anyway so we could hear their answer. I'll email them now and see if they can respond to that question here in the forum.