Guillaume Laforge has provided a recent update to what we can expect to see in the upcoming Groovy 2.0 release. I’m sure it’d be more enjoyable live at GR8Conf, but a great read all the same. Some things I’m interested in: Memoization - could have some interesting uses JSON - have used Jackson previously, but built-in is great! New AST Transformatons (@ToString, @TupleConstructor, @ThreadInterrupt) - even more syntactic sugar Multicatch - cuts out even more verbosity InvokeDynamic performance improvements Groovy 1.
Groovy is great for those little tasks where you probably can’t be bothered pulling out your Java tooling. While certainly more useful as part of a larger collection of tools, the script below lets you check if a website is up by simply downloading that page and confirming that there are greater than zero lines of content. //saved as URLCheckUtil.groovy def url = args g = new URLChecker() def status = g.
I’ve currently got a commute that is somewhere near an hour each way, which leaves plenty of time to fill. While I love music, podcasts somehow make the time go quicker as I feel get embedded in the conversation rather than passively listening to music. So listed below are many of the podcasts I regularly listen to. Developer This Developer’s Life Hanselminutes Techzing Live The Java Posse The Grails Podcast Herding Code FLOSS Weekly IT Conversations mixed feed (conferences etc) Tech Entrepreneur Startups For The Rest Of Us The Startup Success Podcast Tech-related Twisted Wire Patch Monday Spark Security Now
When discovering that I’m a keen advocate of Groovy, people sometimes ask … “but why Groovy?” To me, if there’s a job to be done, it shouldn’t always have to be done the same way you would’ve always typically done it, particularly if there is a more interesting and efficient way. The Groovy language is uber-Java, without much of the ugly. It let’s you get straight to your issue of solving a problem, without having to boiler plate up some classes to compile.