why choosing groovy over ruby, python, jython, etc.

[Horst Naujoks]

After a long time programming with object-oriented languages like smalltalk and java I'm on the path to learn something new: object-oriented scripting. Of course, I've some experience with scripting in perl or php. But now, I'm more interested in "real world" usage of languages like groovy or ruby (especially for the "rails" stuff).

So I'd like to know why I should choose groovy over ruby, python, etc?

I know that Groory could be run within a normal java vm and therefore interact with normal java code, but has - compared to ruby - some performance drawbacks. As far as I know, ruby seems to more sophisticated syntax..

I very appreciate the efforts around the new scripting features of the coming java version, but choosing the "right" thing seems not to be so easy.

[Sahana Hussain]

Here is the answer to your question from Sun's site.

http://java.sun.com/developer/technicalArticles/JavaLP/groovy/


****************************************************************
Why Bother With Groovy?

A common question when someone first hears about Groovy is, why bother with another scripting language for the Java platform? Aren't languages like Ruby and Python sufficient? If you know those languages and are comfortable with them, then by all means use them. But, when you modify these to work with the Java platform, you get variants like JRuby and Jython. The area that Groovy is going after are the Java developers who wants to stick to a Java-centric syntax for their scripting needs, typically while prototyping or testing. Not only do you get a Java-centric syntax, though, but you also get Java-centric semantics. The object model, in particular, is based squarely on that of the Java platform's, not imported from another scripting language and force-fitted into the Java VM.
****************************************************************