I shouldn't need to disable a plugin like that. In my opinion, it's something that I should need to explicitly enable if I want it. All it takes is one person on a project accepting the prompts to agree to the ToS for everyone. They know it's problem too because commercial accounts can disable the integration for everyone.
And most of what I said was relating to the direction Jetbrains is moving. As soon as they start adding service based integrations, it's a slippery slope and we could end up with IDEs that depend on calling out to Jetbrains' services to function.
That's the exact opposite of what I want from Jetbrains and keeping that kind of stuff out of the IDE is the reason I pay them every year.
And most of what I said was relating to the direction Jetbrains is moving. As soon as they start adding service based integrations, it's a slippery slope and we could end up with IDEs that depend on calling out to Jetbrains' services to function.
That's the exact opposite of what I want from Jetbrains and keeping that kind of stuff out of the IDE is the reason I pay them every year.