> For a lot of existing Java code, it's as simple as renaming the file to .groovy This causes the program to run in dynamically-typed mode, much sloooower, so

> For a lot of existing Java code, it's as simple as renaming the file to .groovy This causes the program to run in dynamically-typed mode, much sloooower, so why do it? You'd have to add @Static annotations everywhere to get anything approaching Java-like speeds. One of the Apache Groovy project managers has long since wanted to make Groovy statically compiled by default, but that's never going to happen because they're running an unofficial go-as-slow-as-possible in the official upcoming upgrade to Groovy 3.