> groovy, scala, clojure, and kotlin injected some cool ideas, but might have done more harm by cannibalizing the community and proving that just because it run

> groovy, scala, clojure, and kotlin injected some cool ideas, but might have done more harm by cannibalizing the community and proving that just because it runs on the JVM doesn't make it great 1. Apache Groovy gave people closures and builders on the JVM but at the cost of static type checking, and developers happily embraced it. 2. Then Scala came along and showed you could have closures without losing the static type checking, so many developers moved there instead. 3. Then Clojure came and brought closures to the JVM and lost the syntax, but no-one embraced it. 4. Then Kotlin came and showed you could have both closures and builders on the JVM without losing the static typing, and it's now everyone's favorite. 5. Finally, Java bolted on closures and Groovy and Clojure bolted on static typing annotations, but who's using them?