> Go telemetry is an opt-in system
Great job Go. Hat tip and respect for this. Unlike .Net. I will enable this where it is appropriate.
Great job Go. Hat tip and respect for this. Unlike .Net. I will enable this where it is appropriate.
Whoah. Easy there cowboy.
It was not opt-in when originally announced.
After an extended, shall we say, "lively" discussion on Github[1], they did the right thing and made it opt-in.
(N.B. The discussion was heavily moderated and redacted, it was even more "lively" at the time.)
Seems healthy to me.
If they proposed kicking puppies twice a day, and after some discussion decided to not do that would we all be applauding their decision?
About: https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr...
Collected metrics: https://dotnet.microsoft.com/en-us/platform/telemetry
Source code: https://github.com/dotnet/sdk/tree/main/src/Cli/dotnet/Telem...
In either case, many teams have CIs with 'DOTNET_CLI_TELEMETRY_OPTOUT=1' and call it a day even if it makes no difference to them.
> To help us keep Go working well and understand Go usage, please consider opting in to Go telemetry by running go telemetry on. In that mode, anonymous counter reports are uploaded to telemetry.go.dev weekly, where they are aggregated into graphs and also made available for download by any Go contributors or users wanting to analyze the data. See “Go Telemetry” for more details about the Go Telemetry system.
If someone who is genuinely interested in knowing where it is can't click one link for information, what chance do the go team have of people turning it on?>