5 ms·

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

efilife 2y ago
Where is it? I honestly want to know
- maccard 2y ago
  This is a great example of why it's utterly useless. In the link we're discussing, the release notes say: > 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?>
neonsunset 2y ago
FWIW .NET tooling telemetry can be easily opted-out, which the SDK explicitly tells you about, and there is a page that has full list of the kind of data that is collected (CLI usage metrics and tooling crash stack traces). You can also review the metrics yourself. About: https://learn.microsoft.com/en-us/dotnet/core/tools/telemetry https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr... Collected metrics: https://dotnet.microsoft.com/en-us/platform/telemetry https://dotnet.microsoft.com/en-us/platform/telemetry Source code: https://github.com/dotnet/sdk/tree/main/src/Cli/dotnet/Telemetry 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.
- minkles 2y ago
  [flagged]
traceroute66 2y ago
> Great job Go. Hat tip and respect for this 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.) [1]https://github.com/golang/go/discussions/58409 https://github.com/golang/go/discussions/58409
- minkles 2y ago
  [flagged]
- etse 2y ago
  Are you opposed to the process by which discussion can initiate a transition from negative state to positive state? Seems healthy to me.
  - synicalx 2y ago
    To me, even proposing the (extremely obviously) negative state in the first place is a sign of bad faith on the part of the proposer. If they proposed kicking puppies twice a day, and after some discussion decided to not do that would we all be applauding their decision?
    - heromal 2y ago
      Ridiculous. Only you believe those two are equivalent.
      - synicalx 2y ago
        I don't believe those two things are equivalent, that isn't the purpose of an analogy.

efilife 2y ago

Where is it? I honestly want to know

maccard 2y ago
This is a great example of why it's utterly useless. In the link we're discussing, the release notes say: > 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?>

neonsunset 2y ago

FWIW .NET tooling telemetry can be easily opted-out, which the SDK explicitly tells you about, and there is a page that has full list of the kind of data that is collected (CLI usage metrics and tooling crash stack traces). You can also review the metrics yourself. About: https://learn.microsoft.com/en-us/dotnet/core/tools/telemetry https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr... Collected metrics: https://dotnet.microsoft.com/en-us/platform/telemetry https://dotnet.microsoft.com/en-us/platform/telemetry Source code: https://github.com/dotnet/sdk/tree/main/src/Cli/dotnet/Telemetry 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.

minkles 2y ago
[flagged]

traceroute66 2y ago

> Great job Go. Hat tip and respect for this 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.) [1]https://github.com/golang/go/discussions/58409 https://github.com/golang/go/discussions/58409

minkles 2y ago
[flagged]
etse 2y ago
Are you opposed to the process by which discussion can initiate a transition from negative state to positive state? Seems healthy to me.
- synicalx 2y ago
  To me, even proposing the (extremely obviously) negative state in the first place is a sign of bad faith on the part of the proposer. If they proposed kicking puppies twice a day, and after some discussion decided to not do that would we all be applauding their decision?
  - heromal 2y ago
    Ridiculous. Only you believe those two are equivalent.
    - synicalx 2y ago
      I don't believe those two things are equivalent, that isn't the purpose of an analogy.