> ok, I was not aware of that That’s exactly the problem! :-D And as someone with an external view of things I can tell you, it definitely does.
See the problem is not that groovy is slow, we both know it’s fast, we know about CompileStatic. But others do not. And it’s not promoted that way either. As soon as someone is interested and digs into the docs, they will find out about it (like I did). But to go that far someone must be attracted! The manpower thing is totally right. But why? Because noones interested! -> Back to square one. Did you try the lang servers? One is unmaintained, one is just a linter. The third one is somewhat in progress, but does not even have a readily available download (eg. as vscode extension). I don’t want to compile my “ide” to code in a new language. I want to click install and start doing (as so many others do). lG Matthias On 30. Apr 2020, 15:05 +0200, Jochen Theodorou <blackd...@gmx.org>, wrote: > On 30.04.20 10:37, mojo2012 wrote: > > Hello guys, > > > > I've been wondering why groovy is kinda losing ground respectively not > > gaining more traction these days. It's a fine language - so why does it not > > kick off like kotlin? > > > > I think these are one of the reasons: > > * The logo looks kinda year "1990 MS Wordart"-style. When I first saw the > > logo I instantly though "Probably this language is not maintained anymore?" > > ok, I was not aware of that > > > * Almost all Java devs I've been talking about groovy in the last couple of > > months think that groovy is a purely dynamically-typed language. Which in > > fact turns them off so much, that they don't even want to take a closer > > look. > > We have static compilation for now... 4? years. Not sure how to get away > from that in the end. > > > * The development experience is subpar comparing to Java (Eclipse, IntelliJ > > and VSCode). Groovy Eclipse is slow, autocompletion is flaky sometimes, etc > > In IntelliJ it is not bad, Groovy Eclipse I am not using for such a long > time, I cannot tell anything about it. In the end it is missing manpower > I would say here > > [...] > > What can we do to improve the current situation? > > > > # Logo: both the easiest and one of the hardest points at the same time. But > > I would like a kotlin/vscode/c# inspired logo :-) > > fat blue star with a G? > > > # Promote @CompileStatic more, emphasise that performance has not to be "way > > slower" than java. > > even the dynamic mode is (depending on the scenario) almost as fast as > Java. We do not really static compilation for that. > > > Integrate a language-level "async"/coroutine support, > > like Dart/C# etc have it. > > yeah... that was on my "next thing to do" before Pivotal decided to > discontinued its support for Groovy - which forced me to spend all my > time with other things. It is just a matter of doing it in the end. > > > # Make IDE-integration a part of the groovy project, maybe by providing an > > official Language Server implementation and IDE integrations (like Dart or > > Haxe do) > > langserver.org shows 3 implementations. Did you try them? > > bye Jochen >
