I found the slack support for JetBrains to be absolutely fantastic. Super helpful and very technical. Having written plugins for both VSCode and JetBrains I prefer the latter but I have a heavy Java bias.
I agree that the multi-IDE strategy is problematic. They usually offer an option to just install plugins but with CLion they kind of dropped the ball. Which is surprising because I run their rust plugin on IntelliJ and it works well. Hopefully they'll address that too.
You had one job JetBrains -> speed up developers. I dont need half of the features available. Terminal does a better job at most of them and will never change.
But for the stuff I need and is used by millions if not tens of millions of developers.. just keep it working.
I feel like its slowly the time to move to VSCode. An army of JS Devs will keep on updating it.
https://github.com/intellij-rust/intellij-rust#compatible-id...
I understand the same goes for yet a third branch, which is .Net, and possibly a fourth, which is AppCode. But I don't have any contact with those ecosystems, so don't really know.
They do a lot of smart engineering around the editor: https://code.visualstudio.com/blogs/2018/03/23/text-buffer-r...
What if those remaining 10% are essential to your productivity ?
Like, will it autocomplete in my Django projects the way Pycharm does with models, up to their relations ? If so I may give it a try.
IntelliJ simply could do C/C++ but they chose to push people towards a new IDE... C Lion. That was a huge blow for me, a polyglot.
Then I had a couple of bug opened with them... it took years for them to fix it. Except they marked it as fixed and it was indeed not fixed... Years later!
I kept paying until that point, I just couldn't do it anymore.
The company is a victim of its own success if you ask me. And that's a shame.
VSCode isn't perfect, but it does 90% of what IntelliJ does, and arguably 40% of it better. Also VSCode is faster which still boggles my mind as to how that's possible. I suppose the buttload of cash that Microsoft has thrown at it probably helps there... Since IntelliJ went through their "milliseconds latency blabla" years ago, it's gone downhill.
I imagine that retina pixel displays + java 2nd class child on the macOS platform = big oof (pre-metal).
I dream of a native vscode-like IDE...