Hacker News Reader

Love VSCode however had to start working with a Grails stack this year. Support for groovy and gsp not there but they are working on it... Rather, there seems to be movement in tackling the JVM based languages running along side each other. And by they I mean the various teams working on the extensions under the "Java Support" umbrella.

View on HN

Not sure if any of those "Java Support" teams are really working on Apache Groovy support for VSCode -- they would be working on supporting growing JVM ecosystems (e.g. Java 11, Scala, Kotlin), not declining ones. Virtually every Grails stack out there is still using version 2, even though version 3 was released well over 3 years ago -- a sure sign of a declining ecosystem. Is the Grails stack you're working on any different?

It has been upgraded to Grails 3. I can't speak to the wider Groovy and Grails recent trends(I know they have been trending down in recent years), however Grails development seems to be picking up a bit and I'm certainly going to be dealing with it for the foreseeable future.

VS Code's Java support actually works really well now with a few rough edges based on a mostly Java project I was working with today. Unfortunately even when components are largely Java, a lot of testing and build scripting(Gradle) will be in Groovy. The terseness is nice for sure.. But it means leaving VS Code for IDEA.

Reply on news.ycombinator.com