| Unless I’m missing something, there were 3 issues related to this plugin: 1) The inability to totally remove this core plugin. 2) This core plugin seemed to be reenabling itself after it was disabled. 3) A concern about data being exfiltrated by this plugin while being enabled, but not configured. The answers being: 1) It’s a core plugin - such plugins cannot be disabled. 2) This was a bug that will be fixed in the next release. 3) The plugin did not send any data up unless it had been fully configured. Much of the alarm seems to be revolving around the 3rd issue which seems to have garnered most of the attacks. The biggest issue that I see is not the plugin myself, but JetBrains response (or lack thereof). Folk complained about loosing trust with JB over the fear of 3) I get it, but don’t get it. Apple fucked up years ago with the whole battery gate crap when they made changes to fix an issue but didn’t tell anyone. I’m still using Apple devices and I’ll still continue to keep my JB subscription. Sure JB shot themselves in the foot over a lack of communication, but unless someone can show me otherwise, it looks like no data was transmitted by the plugin unless it had been fully configured. |
For number 3 we will have to take them at their word which, to my mind is not worth a lot at this stage as they have a clear incentive not to follow through on that. They want to generate their own models to be used in their products. What better way to garner data than to have their already good autocomplete make suggestions and then the developer uses them and it is then send of to the server to train models.
In general, as said, I don't mind the occasional bug, BUT when it is vital to be fixed where the vendor has a clear incentive not to fix it as it would be in their favor and where they force something like that upon someone it is different. In such situations I call bullshit. There the vendor has be presumed hostile.
As for the thing you said about Apple. A) I don't use their products. Where I have clout I even advise/discourage/actively go against Mac-products. B) And this is most important. It is whatabout-issm. Just because someone else did it does not make it right.
We, as societies and professionals that hold a lot of the keys to what goes and does not go in society have have to own up to our responsibilities.
What am I to say to my neighbour who is a professional writer when an AI takes his job or the truck-driver that is out of a job because of that or the woman next door that lost their child or husband to one of Tesla's autopilots that they unleashed on the public for beta-/or even alpha-testing knowing that it has bugs that can cause the loss of limb and live? Those engineers,PMs and Managers that go along with that are nothing but despicable to use a generous term.
And here we are : Jetbrains plays the game as well now, muddies the water, pleads ignorance and hopes it can keep the hand in the cookie-jar. Next time around they might be more creative. They can already say that it is YOUR responsibility for keeping your employer's code-base save and YOU should've know better. And they will not thank you for doing your part of being a sucker and helping them build a product they will make millions with. They will laugh all the way to the bank as you still pay them.
The Whataboutism of your's mentioning Apple aside: You basically say that you don't care who falls under the bus as long as you can have it as commfortable as possible. The IP that your employer entrusted you with to keep safe? Na!! Hubub... I wanna plead ignorance, play the sucker, pay for being the product and not think and not be disturbed in my comfort-zone.
I would not hire people that are non-conscientious or critical willing to throw everything aside for their convenience. But... to each their own I suppose, at least do yourself and others around you a favor and be honest about it. Don't utilize strawmanarguments such as whataboutisms to justify decisions.