Totally agree. Telemetry has been around and matured and benefits users. I’m not...

masklinn · on Feb 8, 2023

> Telemetry has been around and matured and benefits users.

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.

jiggawatts · on Feb 8, 2023

Microsoft deprecated the disk-image backup in Windows 7 because it was infrequently used... buy random grandparents.

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.

arp242 · on Feb 8, 2023

There is a long list of use cases, which go far beyond "removing features": https://research.swtch.com/telemetry-uses

"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".

JetSpiegel · on Feb 9, 2023

> Is it safe to remove support for X?

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.

xh-dude · on Feb 8, 2023

I don’t like this example in particular because observing too much “restore” activity is an excellent piece of information.

masklinn · on Feb 9, 2023

I fail to see what’s that got to “too much” restore activity doesn’t tell you anything actionable about your software, if anything it’s creepy as hell.