I'm not sure why, but nobody I know uses this setup – everybody has 2–3 separate IDEs (one for backend, one for frontend etc).
The initial reason behind having separate IDEs for every language, or so I was told, was using different keybindings. This way, XCode users could easily switch to AppCode, Visual Studio users – to Rider etc. – without the need to re-learn anything. (This is the reason I still have Atom keybindings in my Codium setup.)
But why would anyone want to use different IDEs with different keybindings is a complete mystery to me.
I may be mistaken but AFAIK plugins are not always at feature parity with the full jetbrains IDEs. For example the rust plugin in intellij did not support debugging but the one in CLion did (I think this is fixed now).
The python plugin in intellij was a little inferior to Pycharm for Django (pycharm had deeper support for the django ORM) and so on.
I think the reason for the difference between clion and idea for the rust plugin is that clion seems somehow different "on a lower level". It still has support for profiling and valgrind, which Idea lacks [0].
Regarding Django, do you have some examples? I'm admittedly not a hardcore Django user, but I haven't seen any difference between the two.
CLion isn't the best comparison here, as there are some architectural differences between CLion and the other IDES (IntelliJ, PyCharm, WebStorm, etc), which is the reason there isn't a C/C++ plugin for IntelliJ.
That’s absurd! I’ve used the same IDEA Ultimate instance for all languages I touch. Often 3 in the same project. Haven’t seen the point of having separate IDEA/Webstorm/Pycharm instances when one delivers all the functionality of the others.
I’m looking forward to Fleet, watching it closely. But it still has some kinks preventing me from adopting it. Once they polish up the elixir-ls integration I’ll give it a serious shot.
Like my sibling described there are weird quirks. The bigger problem is that this isn't a well documented and supported path. And if you wanted to spend time fiddling with my IDE you wouldn't be using Jetbrains.
The initial reason behind having separate IDEs for every language, or so I was told, was using different keybindings. This way, XCode users could easily switch to AppCode, Visual Studio users – to Rider etc. – without the need to re-learn anything. (This is the reason I still have Atom keybindings in my Codium setup.)
But why would anyone want to use different IDEs with different keybindings is a complete mystery to me.