4 ms·
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
by microflash 3y ago
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?
- chris_st 3y agoI'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?
- microflash 3y agoI was talking more in context of bundled plugins which can't be uninstalled.
- lazide 3y agoApparently (per other posts), it changes the app signature for some platforms and ‘breaks’ the install.
- rschiavone 3y agoThe solution would be not to bundle the plugins then
- ffsm8 3y agoThat'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
- drpossum 3y agoI wish they would. They have a billion products many of which are just slightly incoherent flavors of one another.
- speleding 3y agoThe 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.