4 ms·
I see Jetbrains' role first as a curator of a near flawless collection of plugins for a given purpose. I'm not surprised the set of plugins is different for ea
by gorjusborg 6y ago
I see Jetbrains' role first as a curator of a near flawless collection of plugins for a given purpose.
I'm not surprised the set of plugins is different for each use case. I don't need a Java IDE with CMake plugins, so I don't care if latest CMake plugin conflicts with the Maven plugin (as an example). I'm not _sure_ this is the motivation for per-language products, but I strongly suspect it is.