Comments on: Taking a look at Groovy http://blog.thejit.org/2009/04/21/taking-a-look-at-groovy/ Data Visualization, JavaScript and Computer Science related stuff Sat, 10 Jul 2010 06:02:06 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Nicolas http://blog.thejit.org/2009/04/21/taking-a-look-at-groovy/comment-page-1/#comment-344 Nicolas Wed, 22 Apr 2009 21:03:24 +0000 http://blog.thejit.org/?p=639#comment-344 Hi, thanks for the reply. I really like Ruby, but I don't have any JRuby experience, and I though that since Groovy was initially designed to be built on top of the JVM, its syntax and semantics could perhaps take more profit of that and make Java interoperability intuitive. The result was that for what I was doing at work it served its purpose just like Ruby would have, although its optional typing made me feel more comfortable when dealing with Java classes. Perhaps there are other subtleties that I didn't take into account that make Groovy more suitable for the JVM, although honestly I don't know them. There was howewver an interesting discusion at reddit about this, here: http://www.reddit.com/r/programming/comments/8ei2d/taking_a_look_at_groovy/c0919xs and here: http://www.reddit.com/r/programming/comments/8ei2d/taking_a_look_at_groovy/c091a3t Perhaps that can answer your question :) Hi, thanks for the reply.

I really like Ruby, but I don’t have any JRuby experience, and I though that since Groovy was initially designed to be built on top of the JVM, its syntax and semantics could perhaps take more profit of that and make Java interoperability intuitive.

The result was that for what I was doing at work it served its purpose just like Ruby would have, although its optional typing made me feel more comfortable when dealing with Java classes.

Perhaps there are other subtleties that I didn’t take into account that make Groovy more suitable for the JVM, although honestly I don’t know them.
There was howewver an interesting discusion at reddit about this, here: http://www.reddit.com/r/programming/comments/8ei2d/taking_a_look_at_groovy/c0919xs

and here:

http://www.reddit.com/r/programming/comments/8ei2d/taking_a_look_at_groovy/c091a3t

Perhaps that can answer your question :)

]]> By: Mike Stone http://blog.thejit.org/2009/04/21/taking-a-look-at-groovy/comment-page-1/#comment-342 Mike Stone Wed, 22 Apr 2009 20:51:39 +0000 http://blog.thejit.org/?p=639#comment-342 I tried Groovy a while ago and I liked some things, but disliked others. The seamless integration with Java is really neat, but if I need one way access to Java... I would much rather just use JRuby. If you are interested in my extended thoughts on Groovy... check out http://smellsblue.blogspot.com/2008/06/thoughts-on-groovy.html I tried Groovy a while ago and I liked some things, but disliked others. The seamless integration with Java is really neat, but if I need one way access to Java… I would much rather just use JRuby. If you are interested in my extended thoughts on Groovy… check out http://smellsblue.blogspot.com/2008/06/thoughts-on-groovy.html

]]> By: Rafael George http://blog.thejit.org/2009/04/21/taking-a-look-at-groovy/comment-page-1/#comment-341 Rafael George Wed, 22 Apr 2009 20:14:14 +0000 http://blog.thejit.org/?p=639#comment-341 Hi, i found your article very informative, but i was wondering why didn't you take a look at jRuby you already know Ruby as you mention and you will have the same interoperability with it than with Groovy. Regards. Hi, i found your article very informative, but i was wondering why didn’t you take a look at jRuby you already know Ruby as you mention and you will have the same interoperability with it than with Groovy.

Regards.

]]>