Static vs Dynamic Groovy

If you try groovy++, the results do bare out. And it will add static checking to your code inside of eclipse, which could be argued is more important than adding more servers.

However, it looks like groovy is adding first class support for the functionality in 2.0. Though it seems static checking will be in first and the performance improvements will happen later.

See the reference links below for the relevant blog posts. They provide a good read.

I don’t believe in the groovy purist claims that static checking is not wanted, nor needed. Groovy will die or languish in agony if it isn’t improved. After all, look at Java. As Scala and Clojure and Groovy pick up steam, Java will be used in antique programs and applications that no one wants to convert and new things will hopefully be written in a more terse language.

References

• http://code.google.com/p/groovypptest/
• http://stronglytypedblog.blogspot.com/2010/02/java-vs-scala-vs-groovy-vs-groovy.html
• http://www.jroller.com/melix/entry/groovy_static_type_checker_status

Published by map[name:Sean Wesenberg uri:https://plus.google.com/111523202047342274226] 3 Dec, 2011 and tagged Code using 148 words.