People act like they discover telemetry in 2023.
I don't think it's a big deal, ultimately it's to improve Go and the proposal makes it very easy to disable it ( single env variable ).
People act like they discover telemetry in 2023.
I don't think it's a big deal, ultimately it's to improve Go and the proposal makes it very easy to disable it ( single env variable ).
Does it? Telemetry mostly seems used to justify removing features I need on grounds that they’re little used.
As an other user noted, if telemetry is your yardstick, the average backup software removed the “restore” feature because that’s barely ever used.
"Is it safe to remove support for X?" is one use case. Right now the strategy more or less amounts to "remove and see if anyone complains, possibly too late to change".
What the hell, it's a freaking compiler. What do you mean, "too late to change"? Fail the compilation is suddenly a showstopper bug?
If go wants to deprecate features, just follow the same procedure done by literally all other non-spyware compilers.
It was basically a "free" wrapper on top of the Volume Shadow Service (VSS) built into the operating system, but only IT professionals ever used it, so... it had to go.
These are both Microsoft products. Microsoft's position is well known.
> Java etc ...
Really? Which Java distribution?
It's definitely opt-in in Jetbrains IDEs.