- Andrew Kos
- Bill Burlein
- Bryan Williams
- Christian Vozar
- Jeff Brown
- John Kraus
- Joseph Mak
- Mark Daugherty
- Matt Van Bergen
- Melissa Geoffrion
- Michael Kang
- Michael Chan
- Michael Hodgdon
- Mike Motherway
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Ryan Lunka
- Tom Kelly
Groovy is like Gravy, except that it has the “Groove” in it
Wednesday, December 24, 2008
My five year old daughter, Meredith, recently asked me what I was working on. “I’m just working on some Groovy stuff”, I responded. She then announced: “Groovy is like Gravy, except that it has the ‘Groove’ in it”.
Besides being an outright adorable thing to say, I’m surprised at the level of truth embedded in it. As my first year of using Groovy draws to a close, I can see that duality in Groovy.
Indeed, in the realm of Java, Groovy can act simply as “gravy”, innocuously living along side existing Java code, harmlessly lending closure support and providing more flexible syntax.
Then on the other hand there is the full-tilt “Groove” aspect of Groovy where you can use Metaprogramming to write DSLs, and generally change the way the language behaves at runtime.
Who knows? Perhaps Meredith has sat in on these talks. That would explain her sudden interest in Expandos…
- Invisible requirements within Business requirements
- Building a better Options Predicate
- Extensionless URLs with Adobe Experience Manager
- The Life of a Tester in Adobe CQ World!
- Limitations of the CQ Parsys Model and the Implementation of a Nested Paragraph System
- Using Apache FOP to generate a PDF document based on a form submission data
- Configuring SAML in AEM 5.6
- Why You Should Get the WCM Experts Involved Early