Hmmm...
I had the oppostie reaction to Groovy. Groovy feels Pythonish with a Java
flavor. It felt pretty comfortable. I have not done much with it. What
bothers me about Groovy is the poor set of docs and lack of good IDE tools.
Python by contrast is well documented (or at least better than Groovy). I
could never get my head around Ruby... I just did not like it (I think
mostly becuase it was not Python). I am sure that would change with a Ruby
project or two under my belt, but....
I have not done that much Groovy. Lately, I mostly work with Java. I feel
the productivety gain while using dynamic langauges is not as good as the
productivty gain by using a good Java IDE. I'd rather have a good IDE then
less lines of code. I realize that this may put me in the minority on this
list but.... I am use to it.
:o)
--Rick Hightower
----- Original Message -----
From: "William H. Mitchell" <[EMAIL PROTECTED]>
To: <jug-discussion@tucson-jug.org>
Sent: Friday, August 10, 2007 11:17 PM
Subject: Re: [jug-discussion] Hi guys.... Crank Crud Intro... JPA/JSF Crud
tool
I can't recall the name of the Rails adjunct that provided Grails-like
scaffolding.
I have to say that I like Grails' class-first approach better than Rails'
table-first approach but it'll be interesting to see what the Grails guys
come up with for migrations. (At NFJS Jeff Brown said they're working on
it...)
A little OT...I've been working through "Groovy in Action" and hardly a
session with Groovy goes by without an unpleasant surprise or two. When
learning Ruby there were numerous times when my intuition was correct
about how two pieces would fit together. With Groovy it seems like I'm
constantly out of step.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
