You can disable this plugin but its mere existence can spook legal to force a ban pending "evaluation" and "compliance clearance". I should be able to uninstall it completely.
Unrelated to this, I've been getting repeatedly irked by JetBrains' insistence that I update disabled plugins alongside IDE updates. Why would I want to update stuff that I don't use?
I'm guessing the idea is that yes, it's disabled now, but if you really didn't want it, you remove it (except for AI, of course, which you can't). If you have it installed, why not keep it up to date, so when you decide you want it you have the latest version?
That's would mean homogenizing all jetbrains ides, as theyre all essentially the same program with a different set of bundled plugins, optimized for web, Jvm, c, Python etc
The article mentions that removing a bundled plugin would break the code signing. I suspect allowing you to not update a bundled plugin poses a similar problem, they probably have a single signature for the entire package including bundled plugins.
Unrelated to this, I've been getting repeatedly irked by JetBrains' insistence that I update disabled plugins alongside IDE updates. Why would I want to update stuff that I don't use?