We have just updated Gradle to internally use Groovy 1.6. There are a
number of reasons why we did this. One was that some of our users want
to use 1.6 features in the build script.
Unfortunately this has a big impact on the startup time of a Gradle
build. It takes about 40 percent longer for a hello world build to
execute. The Gradle build itself, with its large number of integration
tests, takes now over 17 minutes compared to 12 minutes and 45 seconds
with Groovy 1.5.6. I know that this is a trade off for the runtime
performance improvement of Groovy 1.6. But I think there is a major
usage scenario for Groovy, where the startup time is important and
not so much the runtime performance. I would be more than happy to
trade Groovy startup time against Groovy execution time for Gradle.
Are there any plans to achieve an improved startup time for future
versions of Groovy? Unfortunately startup time is usually not measured
in all those benchmark comparisons between the different new JVM
languages (I know that Groovy has still the lead in this field, but
better is better). But for real life I think startup time is very
important.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
