One of the things that has been disturbing me for some time now about IDEA has been the apparent focus on other languages at the expense of new features in IDEA's Java support.
At least, that's the way it seems from my perspective.
So I was excited to see the new code-completion feature, and thought I would vote for one of the feature requests related to it because it sounded like a good idea.
In the process, I ended up reading comments from JetBrains representatives such as the following:
"So, do you suggest different behaviors for different languages? I'd say that will prevent a user from establishing any kinds of automaticity, and thus is not acceptable"
"Too bad. I understand your problem, in fact, in Java I have the same one. But I see no solution to it right now. Having a setting or different behavior in different languages seems unacceptable to me for the reasons I already explained"
Note that it is not my intention here to call out this person individually or talk about the feature itself - I am asking here about JetBrains' philosophy in general to this kind of situation.
It was disappointing to me before when I felt like Java support was stagnating because so much effort was being spent on other languages.
But to see JetBrains actively arguing against cool/useful features for Java because it would be too hard to do for other languages? Or just because it would make the experience different between the two languages?
Is that the future of IDEA? Do we only get new Java features if they can be implemented easily in or are consistent with whatever new language is popular this month?