Kotlin: It’s the little things
m.signalvnoise.com
m.signalvnoise.com
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.
After reading just now I found that Kotlin is a JVM language and a project developed by JetBrains. For me the notable language feature is the null handling.
Would I be helping or hurting my facility with Java by using Kotlin for personal projects instead of Java?