Hi Phil, you will peobably want to Take a look at Groovy++ for interest :)
Cheers, Martijn On Saturday, 7 May 2011, phil swenson <[email protected]> wrote: > I was thinking about this the other day - why is groovy never > mentioned as java.next? > > then today I saw this nice write up on groovy as "java.next()": > http://batsov.com/2011/05/06/jvm-langs-groovy.html > > I've been doing a lot of groovy lately as we are reworking our entire > build/test/automation system in gradle. I really like the > language.... it's much more enjoyable to code in that java. Not only > is the language nice, but they cleaned up a lot of crappy Java APIs. > All the stuff that apache commons does to make what should be simple > data structure/file/xml/string/io tasks easy, groovy monkey patched to > provide directly in the Java APIs. (e.g. File.text reads in a file as > a string) > > *BUT* I don't think it's java.next. If groovy had decided to do > static typing way back when I think it would already be java.next (w/ > optional dynamic typing). But they didn't so it's simply too slow... > and a dynamically typed language will never have the quality of IDE > tooling that Java enjoys. Just isn't doable. > > -- > You received this message because you are subscribed to the Google Groups > "The 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 "The 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.
