There is a lot of talk around about Groovy v. Ruby v. Java, and I reckon a lot of it is missing the point. I like Groovy because it was built from scratch to play great with Java. I can use it now in unit testing (one of its original use cases, and a potential killer app for it IMHO). It is a nonsense to even consider fighting battles with Java, or Ruby – why bother? It is a great tool in our toolbox, use it appropriately. I’m using it for unit testing, I’m using it for scripting within products. It will not replace Java, neither will Ruby. The fundamental advantage of Java over Groovy and Ruby is that it is statically typed, which – amongst other things – enables (note my use of the word “enables”) good tooling. While Ruby is hot right now, I think Groovy is in a different league, its going to be a slow burner, but in the end may burn more brightly and for much longer.
3 Responses to “The pointless Groovy v. Ruby v. Java argument”
Recent Posts
Blogroll
Top Posts
- From GoDaddy to Google Apps in 20 minutes
- Thankful for Steve at Thanksgiving
- Not convinced about Guice, Spring scores again with JavaConfig
- Groovy email
- Please vote for the ULTIMATE Java/Groovy/Ruby development Laptop
- Groovy+Grails slaughters Ruby+Rails in performance stakes
- The pointless Groovy v. Ruby v. Java argument
- Automated Eclipse GUI testing the quick and simple way
- OSGi server side and servlets
- Eclipse workbench in a browser?
Archives
- November 2009
- October 2009
- June 2009
- April 2009
- January 2009
- December 2008
- November 2008
- October 2008
- August 2008
- July 2008
- June 2008
- May 2008
- March 2008
- February 2008
- January 2008
- November 2007
- October 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- January 2006
- October 2005
- September 2005
- August 2005
- June 2005
- October 2004
- June 2004
- April 2004
- January 2004
- December 2003
In the immortal words of Ed McMahon “YESSSS!”
Don’t you mean: HIYOOOOOOOO!
For me the main issues are speed and productivity. Static typing gives you more speed when making apps like simulations. Productivity I guess both groovy and ruby are better than java though, although again with static typing you get things like better code completion support in an IDE.
So I’m looking forward to trying statically typed languages with type inference, like F3 and maybe fortress: http://edtechdev.blogspot.com/2007/01/f3-new-statically-typed-scripting.html