Although I will vote up the Groovy issue you detail, being a long-time IntelliJ user, I can tell you first hand that upvoting an issue at JetBrains has no effect I am aware of. I have seen critical issues get hundreds of votes and remain untouched for years. They do what, when, and how they like.
On Wed, Mar 11, 2020 at 11:27 AM MG <mg...@arscreat.com> wrote: > Hi guys, > > up to this point, the first issue I created two days ago (see previous > post for link) has gotten zero votes - if no one is voting for these > issues, then it makes no sense for me to put them up, so please do not > only vote for the umbrella issue (which just got vote 37 - still > incredibly low given the large number of Groovy users out there), but > for each individual issue as well. > > Consider to not only vote for the features you yourself would > immediately use - all of these features were included after some > discussion, because they were considederd to make Groovy a better > language, and some things need time to establish themselves, but there > is no chance of that happening, if the most prevalent Groovy IDE marks > the code as invalid and accordingly offers no > Intellisense/refactoring/etc support*. > > Cheers, > mg > > *I keep wondering what people new to Groovy think, if they try to use a > feature introduced nearly 2 years ago, but their IDE marks it as invalid > code... > > > > > >
