[enricopulatzo]

Groovy could really benefit from a marketing team. More and more blog posts about the nice sides of Kotlin offer snippets and arguments that have been in Groovy 2 for a while now. Good job on the Jetbrains folks for clearly doing a better job advocating their language as a replacement for Java.

[vorg]

Apache Groovy's lack of marketing is highlighted by the fact you're referring to it as "Groovy" instead of "Apache Groovy" which is what the Apache Software Foundation (ASF) recommend it be called on first use in all new contexts.

Groovy's controllers decided 2 years ago when they joined the ASF to simply milk the product while prolonging its lifespan as long as possible, rather than improve and promote it. It's obvious to everyone Groovy's on an irreversible decline:

* no-one uses the static typing features of Groovy, in fact none of the Java code in Groovy itself has been re-written in statically-typed Groovy

* virtually no-one's upgraded from Grails version 2 to 3, or starting new projects in Grails

* Gradleware are no doubt working on a tool to automatically convert Groovy build files to Kotlin ones for their next major release of Gradle, and thus also Android Studio, now that Google have chosen Kotlin as its preferred language for Android

Groovy will probably be used for basic scripting and gluing on the JVM for quite a while though, in the same way Bash is used for Linux.

[tmd83]

But it's quite different from Groovy isn't it. It's static typed like Java and it's performance should be much closer to Java and not like Groovy. Even if a lot of the language features are there in Groovy these two ought to make a whole lot of different to Java crowd.