"Isn't one of the most
fundamentally attractive qualities of Groovy/Grails that they build on the
foundation of everything that Java offers, while adding many of the dynamic
language benefits people extol from Ruby/Rails, etc?
If I have understood correctly, the person who has invested years in building
Java expertise loses little or nothing in a move to Groovy/Grails, but a jump
to Ruby/Rails would imply a near-total reset. Similarly with tools and
libraries - all your Java stuff just keeps on working.
Maybe 'replace' isn't the right verb? Perhaps it is 'enhance' or something more
positive that incorporates the best of Java's solid foundation and adds
valuable new semantics and paradigms?"
-- Rick Ross