4 ms·

> Dead It's being maintained. A new version (3 iirc) is about to come out. But it's not a hot bed of innovation. I think Kotlin now already has a lot more min

by cies 7y ago

> Dead It's being maintained. A new version (3 iirc) is about to come out. But it's not a hot bed of innovation. I think Kotlin now already has a lot more mindshare and corporate interest behind it than Groovy ever did.

pjmlp 7y ago
Groovy had first class support on Spring and Sun was doing talks at JSFDays on how it would become the JEE scripting language. Those of us that are part of the Java world since the early days, have been through this multiple times.
- The_Colonel 7y ago
  > Those of us that are part of the Java world since the early days, have been through this multiple times. Right, history repeats itself all the time ... until it doesn't. 10 years ago is not now, Kotlin is not Groovy ...
  - pjmlp 7y ago
    Indeed, Groovy did not had an OS to sell it alongside.
- imtringued 7y ago
  Grails is 13 years at this point and still the only way to take advantage of the JEE Java ecosystem while also leaving your sanity intact. Since Grails 4 it is slowly moving away from Spring to Micronaut so the JEE ecosystem may die before Grails does.
  - pjmlp 7y ago
    That is irrelevant for Java as platform and programming language, just libraries that come and go, Java stays. Just like C on UNIX, JavaScript on the browser, ....
- dajohnson89 7y ago
  don’t forget gradle and jenkins
  - BossingAround 7y ago
    Gradle is moving to Kotlin. I would be surprised if Jenkins wouldn't follow to move away from Groovy.
- zmmmmm 7y ago
  > Those of us that are part of the Java world since the early days, have been through this multiple times. The hype curve is definitely in the past, but Groovy is living on quite well as a small but viable option in the plateau of productivity. In some ways that is more important because while in the hype phase it is really hard to judge the true value of a technology. The true value emerges when the hype is over. The problem is, there isn't really a better scripting option for the JVM. While in theory lots of JVM languages (JRuby, Jython ... etc) could fill that gap, they all have ugly impedance mismatches which Groovy doesn't, so companies continue to deploy it as a scripting and DSL implementation still. I tried to substitute Kotlin for a bit and went back to Groovy because Kotlin still lacks standard scripting constructs such map and list literals etc.

by cies 7y ago

pjmlp 7y ago

Groovy had first class support on Spring and Sun was doing talks at JSFDays on how it would become the JEE scripting language. Those of us that are part of the Java world since the early days, have been through this multiple times.

The_Colonel 7y ago
> Those of us that are part of the Java world since the early days, have been through this multiple times. Right, history repeats itself all the time ... until it doesn't. 10 years ago is not now, Kotlin is not Groovy ...
- pjmlp 7y ago
  Indeed, Groovy did not had an OS to sell it alongside.
imtringued 7y ago
Grails is 13 years at this point and still the only way to take advantage of the JEE Java ecosystem while also leaving your sanity intact. Since Grails 4 it is slowly moving away from Spring to Micronaut so the JEE ecosystem may die before Grails does.
- pjmlp 7y ago
  That is irrelevant for Java as platform and programming language, just libraries that come and go, Java stays. Just like C on UNIX, JavaScript on the browser, ....
dajohnson89 7y ago
don’t forget gradle and jenkins
- BossingAround 7y ago
  Gradle is moving to Kotlin. I would be surprised if Jenkins wouldn't follow to move away from Groovy.
zmmmmm 7y ago
> Those of us that are part of the Java world since the early days, have been through this multiple times. The hype curve is definitely in the past, but Groovy is living on quite well as a small but viable option in the plateau of productivity. In some ways that is more important because while in the hype phase it is really hard to judge the true value of a technology. The true value emerges when the hype is over. The problem is, there isn't really a better scripting option for the JVM. While in theory lots of JVM languages (JRuby, Jython ... etc) could fill that gap, they all have ugly impedance mismatches which Groovy doesn't, so companies continue to deploy it as a scripting and DSL implementation still. I tried to substitute Kotlin for a bit and went back to Groovy because Kotlin still lacks standard scripting constructs such map and list literals etc.