Making Go telemetry opt-in is a mistake

Re:Making Go telemetry opt-in is a mistake by fortyseven on Sunday February 26, 2023 @09:20AM (#34945727)

As someone who was considering getting some Go and Rust under his belt, they've saved me a lot of time. This whole telemetry nonsense has ensured I won't waste my time investing it in Go. Great job.

[ Parent | on HN ]

Re:Making Go telemetry opt-in is a mistake by Operyl on Sunday February 26, 2023 @09:48AM (#34945926)

Uh, what? The Go team introduced an idea, opt out telemetry with a one week delay before it was sent. Users said it wasn’t great, overwhelmingly. The Go team heard the feedback and made it opt in. What’s the problem, that’s a good thing.

[ Parent | on HN ]

Re:Making Go telemetry opt-in is a mistake by Patrickmi on Sunday February 26, 2023 @01:05PM (#34947682)

People are naive, am sure he doesn’t know that rust has telemetry

[ Parent | on HN ]

Re:Making Go telemetry opt-in is a mistake by twilysparkle on Sunday February 26, 2023 @02:37PM (#34948612)

I'm not aware of rust hanging any telemetry

[ Parent | on HN ]

Re:Making Go telemetry opt-in is a mistake by steveklabnik on Sunday February 26, 2023 @03:16PM (#34948927)

Rustup was going to add it, some work was done, and then it was abandoned.

This was years ago. https://github.com/rust-lang/rustup/pull/1642

[ Parent | on HN ]

Re:Making Go telemetry opt-in is a mistake by twilysparkle on Sunday February 26, 2023 @03:52PM (#34949284)

Interesting. I'd assume that the installer is one of the better places to get this information too.

[ Parent | on HN ]