Back in March of last year, I wrote a post comparing Groovy and Scala. Enough time has passed that I thought it was worth revisiting the topic.
In my original post, I reached the conclusion that at least for me, it made sense to first focus on Groovy and then later learn more Scala. I still feel that way, but my thoughts on the matter have evolved. How about combining Groovy and Scala in the same program or architecture? That thought had vaguely occurred to me already, but it was solidified by the discussion of Twitter’s use of Ruby and Scala. They started off using Ruby (Ruby on Rails, in particular) to run their whole site. When they ran into performance and scalability issues, they determined what was causing the most trouble (back-end tasks) and gradually converted the relevant parts of the system into Scala. This kind of polyglot programming makes sense to me. It follows the principle of “using the best tool for the job.” I think the combination of Groovy and Scala makes even better sense: they’re designed to run and interoperate with other languages on the same VM. Not surprisingly, I’m not the first person to think of this. I found two posts from Andres Almiray (“Griffon: Groovy & Scala working together” and the follow up “Follow up on Griffon/Groovy/Scala”) showing some practical examples and another on a different blog discussing the ability jointly compile “Groovy+Scala+Java”. I’m excited to watch and perhaps participate in these exciting developments.
Side Note: On the subject of Groovy, when my one-year IntelliJ license was close to expiring, I decided to check out NetBeans. I was pleased to discover it had quite good Groovy and Grails support. I’ve been using the 6.7 milestone builds and now the beta, in order to get support for Grails 1.1. If you haven’t tried Groovy/Grails development in NetBeans yet, you should.
Update: Here are links to the items Andres mentioned in the comments
Update (Jan 12, 2010): Andres recently posted the highly relevant Groovy & Scala: a tale of two JVM languages