|
|
|
|
|
by vorg
4083 days ago
|
|
The JVM ecosystem is far bigger than Groovy, Gradle and Grails. Think Scala and Clojure for languages, Spring and Play for frameworks, and Maven for builds. Groovy has 2 big use cases in industry: * scripting to manipulate Java classes, for testing and 50-line scripts in Gradle, though Gradle's been opening up its API so any JVM language can use it. When Java 8 becomes more widespread, a future version of Gradle might standardize on Java lambdas and ignore use of Groovy closures in its DSL * the MOP used by Grails, though Grails is following its namesake Rails into obscurity Although Groovy 2 bundled a statically-typed compiler to compete with Java, virtually no-one uses it. There's far better choices for developers who want to replace Java on the JVM, such as Scala. Groovy really should've stuck to its dynamic roots and niche by adding scripting support for Scala-compiled classes instead of going into head on competition with it and Java. |
|