3 ms·

If there is any virtue to collecting telemetry, make it opt-in. Any developer convinced of this being useful will gladly enable it. But making it opt-out is jus

by _ph_ 4y ago

If there is any virtue to collecting telemetry, make it opt-in. Any developer convinced of this being useful will gladly enable it. But making it opt-out is just nefarious, because most users will not be aware of it.

Thaxll 4y ago
This is naive, no one ever turn telemetry on if it's turned off by default, that's the reason why it's on by default.
- ocdtrekkie 4y ago
  > no one ever turn telemetry on if it's turned off by default If nobody would voluntarily do it, why do you think it's okay to do it at all? By your very admission, nobody wants this. Because if they did, they'd turn it on!
- _ph_ 4y ago
  Still, opt-out is just inacceptable. At least with a mechanism which can easily fail, like setting an environment variable. This basically forces you to wrap the go tool in a script which ensures the environment variable to be set. As this seem to cache the results, another option is to fiddle with the cache to report bogus information.
  - Thaxll 4y ago
    You can set env variable for the go toolchain with a command such as: go env -w TELEMETRY=off which will be written to disk and use by the go cli.
    - _ph_ 4y ago
      Where will it be written to and how is it guaranteed to be picked up by any further invocations of the tools?
    - JetSpiegel 4y ago
      What if a new version of go uses TELEMETRY_ENABLED? Do you read all the changelogs, always?
      - simoncion 4y ago
        Yeah, given go's history with breaking changes (and the habit of OKR-chasing managers and Senior Staff to make Number Go Up to look good on the promo packet), I definitely would not trust any opt-out mechanism to not receive operationally-significant changes in the next five years.
        Thaxll 4y ago
        As far as I known go never changed any flags since release ( 2012 ), is it good enough for you?
      - deleted 4y ago
        [deleted]
- msla 4y ago
  "This is naïve, no one would ever allow me into their homes if I asked first, and how else would I find out what diseases they have?"

by _ph_ 4y ago

Thaxll 4y ago

This is naive, no one ever turn telemetry on if it's turned off by default, that's the reason why it's on by default.

ocdtrekkie 4y ago
> no one ever turn telemetry on if it's turned off by default If nobody would voluntarily do it, why do you think it's okay to do it at all? By your very admission, nobody wants this. Because if they did, they'd turn it on!
_ph_ 4y ago
Still, opt-out is just inacceptable. At least with a mechanism which can easily fail, like setting an environment variable. This basically forces you to wrap the go tool in a script which ensures the environment variable to be set. As this seem to cache the results, another option is to fiddle with the cache to report bogus information.
- Thaxll 4y ago
  You can set env variable for the go toolchain with a command such as: go env -w TELEMETRY=off which will be written to disk and use by the go cli.
  - _ph_ 4y ago
    Where will it be written to and how is it guaranteed to be picked up by any further invocations of the tools?
  - JetSpiegel 4y ago
    What if a new version of go uses TELEMETRY_ENABLED? Do you read all the changelogs, always?
    - simoncion 4y ago
      Yeah, given go's history with breaking changes (and the habit of OKR-chasing managers and Senior Staff to make Number Go Up to look good on the promo packet), I definitely would not trust any opt-out mechanism to not receive operationally-significant changes in the next five years.
      - Thaxll 4y ago
        As far as I known go never changed any flags since release ( 2012 ), is it good enough for you?
    - deleted 4y ago
      [deleted]
msla 4y ago
"This is naïve, no one would ever allow me into their homes if I asked first, and how else would I find out what diseases they have?"