Groovy signals go-ahead for 2.0-beta-1
Static type checking the main improvement for the next generation
Despite possible lexicographical confusion, Groovy has announced that they are dropping the ‘dot’ updates, skipping over 1.9 and going straight onto 2.0, to incorporate a deluge of new features.
Today’s double header announcement paves the way for their next generation of the dynamic language on the JVM, now opting for annual releases for substantial future versions. That means we only have to wait until 2013 for Groovy 3.0. They’ve also promised not to adopt Google Chrome’s or Mozilla Firefox’s ‘lightning fast numbering schemes’.
The main revamp comes in the form of static type checking support functionality. Groovy say that, from feedback they get, they’ve noticed that their dynamic language wasn’t being used for its main purpose but instead as a better syntax for Java. To accommodate this, the compiler flags up issues at the compiling stage rather than at execution time, therefore giving feedback much sooner. A much more in-depth guide for the static checker (codenamed Grumpy) can be found here, and also the GEP 8 (Groovy Specification Proposal) specification of static checking.
Other key proposed features include further investigation into static compiling support and invoke JDK 7 support, which they claim will dramatically improve the dynamic aspects of Groovy. The future for Groovy looks very bright indeed, with the open community relationship really helping innovate the language and progress further, perhaps ahead of other dialects.
Guillaume Laforge announced on Groovy’s blog the release for 1.8.4 as well, brought out to fix and improve problems in the Grails framework and Gradle build automation. More details for both the 1.8.4 and 2.0 are available in the release notes and for download here. Groovy state that nothing is binding yet and that feedback could change or evolve things further.