majorhelmet

> all comes down to whether you trust Google

Not true. The code is open source and everyone can trivially with minimal effort check that they are sending only the data they said they would send.

I still think it depends on the telemetry itself. Companies knowing my location at all times? Disgusting and creepy. Company knowing I ran `go help` 200x as opposed to running `go build` 10x is fine imho.

Users wishes would be respected in both opt-in and opt-out scenarios.

> Some industrial user wants a new Go feature or bugfix? Great. If it's enough of a problem, they can fix it and upstream a patch.

Inbefore I go to a new job and find out that they are using outdated, custom patched go compiler.

> I mean, there are 5000+ issues and 330 open PRs on the go github right now

How do they know which ones are affecting the most users?

> forced google spyware in a compiler

go is open source, feel free to compile it yourself without the telemetry. Which distros will do if any major promises would be broken

Look, I hate large crops too but this paranoia hinders open source's ability to self-cooperate.

> Telemetry coming from this IP, so company x is using go. A pattern of data coming every 2 days, so their build nodes rebuild every 2 days.

Not true. Even if Google lied about collecting IPs, the data would be sent only every ~ year with aggregated counts so no real time usage data. And even if one could see the patterns from the data, everyone will be able to, not just Google.

Let's not trust Google. But let's not shoot ourselves in the foot by refusing any automated cooperation.

Additionally, majority of distros use package managers, so if any of the major promises of the upstream would be broken, distro packages could patch it out. This isn't forced, there are several points where anyone can stop the telemetry.