4 ms·
I think we are in agreement. The problem I have with the principle of forced telemetry is I have no way (or more precisely, time) to understand that their telem
by vivegi 4y ago
I think we are in agreement. The problem I have with the principle of forced telemetry is I have no way (or more precisely, time) to understand that their telemetry red-line stops with command line logging/analysis. So, I have to assume the worst with the toolchain.
Microsoft .NET also introduced opt-out telemetry (ie., turned ON by default and you could opt-out by setting an environment variable DOTNET_CLI_TELEMETRY_OPTOUT=1|true|yes). These are just dark patterns by big-tech and erode developer trust.
Ken Thompson's Turing Award lecture on "Trusting Trust" comes to mind. https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_Ref...
- bayindirh 4y agoBoth of us are completely on the same page. Funnily, I have made the same reference to the same paper [0]. The comment has a "let's talk about how we stop there and not move forward than that" tone, because frankly, I don't think Go maintainers and Google will say "Oh, we overreached, sorry. Let's abandon it and never talk about it again". However, even discussing telemetry and being so adamant about it made me reconsider the extent I'm going to use Go in the future. [0]: https://github.com/golang/go/discussions/58409#discussioncomment-4928702 https://github.com/golang/go/discussions/58409#discussioncom...