3 ms·

When Groovy's author said he prefers Scala (http://macstrac.blogspot.ro/2009/04/scala-as-long-term-replacement-for.html http://macstrac.blogspot.ro/2009/04/scal

by nnq 14y ago

When Groovy's author said he prefers Scala (http://macstrac.blogspot.ro/2009/04/scala-as-long-term-replacement-for.html http://macstrac.blogspot.ro/2009/04/scala-as-long-term-repla...) it pretty much sealed the language's fate... though, in all seriousness, there really is too much language diversity on the JVM (how tf would one choose between Groovy, JRuby or JPython? - yeah, you choose the framework not the language, but still, it means that all the good developers are split working on different projects).

don_draper 14y ago
That statement is misleading. James Strachan left Groovy a long time ago. Guillaume Laforge has lead the project from almost death to one of the most popular languages in use today.
- vorg 14y ago
  Most of the technical work has been done by Jochen Theodorou. Others who have helped technically are Paul King, Cedric Champeau, Alex Tkachman, and Jeremy Rayner. James Strachan also did a lot of technical work on Groovy in his day. I'd rather listen to what someone who's done technical work has to say than someone who shows powerpoint slides. You mentioned Guillaume Laforge as leading the Groovy project, but from my experience, Graeme Rocher, the Grails Project Manager, seems to have far more say over Groovy's direction. As for calling Groovy "one of the most popular languages in use today", it figures fairly low in most popularity ratings (e.g. not in Tiobe's top 50), and only shows the occasional burst when it's been actively talked up, e.g. just before a conference when the project managers are selling conference seats.
zmmmmm 14y ago
That piece is very dated, and your comment is misleading. He didn't consider Groovy as a replacement for Java at the time because it was not statically typed and did not compile to fast byte code. In fact, if you read through all the reasons he recommends Scala, every one of them has been addressed in Groovy in the last few years.
- vorg 14y ago
  Scala did it all first, and has been battle-tested over many years, while Grbdvy's only recently added static compilation. JRuby did invoke-dynamic before Grbdvy, and Clojure did concurrency before Grbdvy's GPars.
vorg 14y ago
> how tf would one choose between Groovy, JRuby or JPython? Look at the key differentiator of each language when it was first created. So, If you really need the JVM... * Groovy for quick-to-write dynamically-typed scripts for testing Java classes * JRuby if you need Java 7 and invoke-dynamic * Scala if you need static compilation * Clojure if concurrency is important Of course, if you need specific software, choose Groovy for Grails, Scala for Lift, Clojure for Leinengen, etc. If you don't need the JVM, consider Ruby, Python, Javascript, etc.

by nnq 14y ago

don_draper 14y ago

That statement is misleading. James Strachan left Groovy a long time ago. Guillaume Laforge has lead the project from almost death to one of the most popular languages in use today.

vorg 14y ago
Most of the technical work has been done by Jochen Theodorou. Others who have helped technically are Paul King, Cedric Champeau, Alex Tkachman, and Jeremy Rayner. James Strachan also did a lot of technical work on Groovy in his day. I'd rather listen to what someone who's done technical work has to say than someone who shows powerpoint slides. You mentioned Guillaume Laforge as leading the Groovy project, but from my experience, Graeme Rocher, the Grails Project Manager, seems to have far more say over Groovy's direction. As for calling Groovy "one of the most popular languages in use today", it figures fairly low in most popularity ratings (e.g. not in Tiobe's top 50), and only shows the occasional burst when it's been actively talked up, e.g. just before a conference when the project managers are selling conference seats.

zmmmmm 14y ago

That piece is very dated, and your comment is misleading. He didn't consider Groovy as a replacement for Java at the time because it was not statically typed and did not compile to fast byte code. In fact, if you read through all the reasons he recommends Scala, every one of them has been addressed in Groovy in the last few years.

vorg 14y ago
Scala did it all first, and has been battle-tested over many years, while Grbdvy's only recently added static compilation. JRuby did invoke-dynamic before Grbdvy, and Clojure did concurrency before Grbdvy's GPars.

vorg 14y ago

> how tf would one choose between Groovy, JRuby or JPython? Look at the key differentiator of each language when it was first created. So, If you really need the JVM... * Groovy for quick-to-write dynamically-typed scripts for testing Java classes * JRuby if you need Java 7 and invoke-dynamic * Scala if you need static compilation * Clojure if concurrency is important Of course, if you need specific software, choose Groovy for Grails, Scala for Lift, Clojure for Leinengen, etc. If you don't need the JVM, consider Ruby, Python, Javascript, etc.