I've been using Groovy for a few months and so I'm no expert. Here's some thoughts so far:
1. Love the POGOs with their automatic getters/setters/constructors. 2. closure syntax for loops is very nice. 3. The map syntax is great, being able to reference a url parameter like this : para.id 4. There's another level - builders, mixins, that I've only fleetingly seen but decided not ready yet. 5. People love to create DSLs but I'm not convinced of their worth everywhere. You need to know the DSL which is only slightly easier than learning the underlying library it tries to simplify. HTTPClient, take note. 6. Had a strange bug yesterday, I was reading json with JSonSlurper, a value representing seconds since epoch was automatically being cast to Integer, which turns out is too narrow because I multipy it by 1000 to get milliseconds (to pass to Date's constructor) but was getting the wrong Date. It was losing precision without complaining. 7. The mock testing situation is not quite good enough. MockFor and StubFor are not good enough. Everyone says use Spock but that's another library to learn. I do feel at times that I am on the cutting edge as I program. I don't feel that with Java as its so stable in day to day use. One use case that I think will be a killer is to create a Groovy library over the Amazon Web Services Java SDK. Thats going to be fun! Overall, I like the syntax sugar and the Java-compatibility over everything else by a mile. I am slightly concerned if it will perform at runtime but I guess I'll have to test that. Rakesh Overall, its nicer than Java on a day to day level. On 2 June 2012 22:25, phil swenson <[email protected]> wrote: > I think groovy is a good name myself. Why does software have to be dry? > > Anyway, Groovy 2.0 will kill Groovy++. > > But I think annotations are the wrong way to add static to the lang. > Guessing they had to for backwards compatibility? Ugly. > As I've said before, I think if groovy had been created as a > statically typed language in the first place, it would be much more > popular than it is. > > On Thu, May 31, 2012 at 7:31 PM, Jon Kiparsky <[email protected]> > wrote: > > It may make me a bad person, or a shallow one, but I cannot conceive of > > learning a language called "groovy". The idea simply turns my stomach. > Could > > they not have come up with a less awful name? Like, maybe "scrotum"? > > > > > > On Wed, May 23, 2012 at 1:11 PM, parentjo <[email protected]> wrote: > >> > >> Hi, > >> > >> During the brief discussion of groovy's upcoming static typing I feel > >> groovy++ deserves to be mentioned as well. It is an extension/ > >> companion for the current groovy release. It retains all of the groovy > >> goodness and adds static typing with a simple annotation. The static > >> typing is both at compile time (*) and at runtime. The lack of runtime > >> enhancements (MOP) gives it a clear performance boost compared to > >> dynamic groovy. > >> > >> I used this in small project and it gives you all the enhancements to > >> Collection API, closures, terse syntax etc of groovy while being typed > >> like java. Personally, that's all I need. > >> > >> It is no clear to me what the "interactions" are between the groovy++ > >> and groovy project since the latter does not seem to refer to the > >> existing groovy++ work much. Politics perhaps? > >> > >> More info and benchmarks at > >> http://code.google.com/p/groovypptest/wiki/Welcome > >> > >> Regards, > >> > >> Johan > >> > >> (*) From G. Laforge's talk @devoxx2011 I remember that initially the > >> type checking will be compile time only. Maybe that changed in the > >> meanwhile. > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Java Posse" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> For more options, visit this group at > >> http://groups.google.com/group/javaposse?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Java Posse" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > > http://groups.google.com/group/javaposse?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
