2 ms·
> And? Nothing "needs" to replace the language, though I think this is a really important thing about JVM langauges. They can exist successfully at much lower
by zmmmmm 8y ago
> And? Nothing "needs" to replace the language, though
I think this is a really important thing about JVM langauges. They can exist successfully at much lower thresholds of popularity because they piggy back on Java. So I don't have to worry about Groovy dying off (which is not to say it is) - because basically as long as Java is around it is going to have access to a giant community of developers. So using Groovy or Clojure or Scala etc is a much lower risk proposition than jumping in the deep end with a stand alone language. In that sense, Groovy / Clojure / Scala / Kotlin don't really compete with each other or Java as much as help each other, and Java's popularity is really the sum of all of them.
- vorg 8y ago> So I don't have to worry about Groovy dying off (which is not to say it is) Apache Groovy is dying off. Whenever some software product bundles it as a built-in scripting language, after a short time Groovy's snags become apparent and that software starts bundling another scripting solution, e.g. Kotlin for build scripts in Gradle [1], or the Declarative Pipeline Syntax for Jenkins [2]. [1] https://docs.gradle.org/5.0/userguide/kotlin_dsl.html https://docs.gradle.org/5.0/userguide/kotlin_dsl.html [2] https://jenkins.io/blog/2016/12/19/declarative-pipeline-beta/ https://jenkins.io/blog/2016/12/19/declarative-pipeline-beta...