Guillaume Laforge: Optimizing performance in Groovy 1.6
Groovy Project Manager Guillaume Laforge 
talks with Andrew Glover about what's new in the Groovy 1.6 beta release. Learn about the complexity that has slowed Groovy
down in the past and find out what's been done to greatly improve benchmark results in Groovy 1.6. Guillaume also shares tips
for optimizing Groovy-based applications and talks about the recent burst of tools support for Groovy; current challenges
for the Groovy development team, and what we can expect from upcoming releases such as Groovy 1.7 and 2.0.
- Groovy Project Manager Guillaume Laforge announces the Groovy 1.6 beta-1 release.
- Scott Davis explains why he believes Groovy is sometimes a better choice than Java on the JVM.
- Venkat Subramaniam used Groovy for many examples in the recent JavaWorld series, Creating DSLs in Java.
- Read a JavaWorld excerpt from Andrew Glover's Groovy in Action.
- Also check out Andrew's IBM developerWorks series, Practically Groovy.
- Stay tuned for more inside views from JavaWorld's Java Technology Insider.
Recent articles:
- Measuring client-side response time
- Java: A platform for platforms?
- OSJP: Java Caching System
- Jump into JavaFX, Part 1
- Spring Web Flow: A boon to JSF developers
Popular archives:
- Inheritance vs composition (1998)
- J2EE object caching frameworks (2004)
- XFire: Easy and simple Web services (2006)
Java: A platform for platforms
Sun's reorg may seem promising to shareholders but it's also a scramble for position. The question now is whether Sun can,
or wants to, maintain its hold on Java technology. Especially with enterprise leaders like SpringSource and RedHat investing
heavily in Java's future as a platform for platforms
Also see:
Discuss: Tim Bray on 'What Sun Should Do'
Archived Discussions (Read only)