News for hackers. Stuff that matters.
Re:Making Go telemetry opt-in is a mistake by speedgoose on Sunday February 26, 2023 @09:02AM (#34945605)
But the users can still report issues.

And Golang also has the yearly survey that gives much more valuable inputs than telemetry could track IMHO.

Re:Making Go telemetry opt-in is a mistake by xena on Sunday February 26, 2023 @09:05AM (#34945620)
Assuming every Go user on the planet fills it out.
Re:Making Go telemetry opt-in is a mistake by speedgoose on Sunday February 26, 2023 @12:26PM (#34947312)
They don’t have to care about the super rare cases, and in practice they never did. The survey has already a more than big enough sample to take the right decisions.
Re:Making Go telemetry opt-in is a mistake by remus on Sunday February 26, 2023 @10:04AM (#34946069)
> But the users can still report issues.

They can, but do they? Russ' very first blog post gave several examples where major issues slipped under the radar because they went unreported. The example that sticks in my mind is that they accidentally introduced a dependency on a c compiler on Mac that was not reported for over a year simply because users assumed it was meant to be a dependency.

Re:Making Go telemetry opt-in is a mistake by pie_flavor on Sunday February 26, 2023 @01:29PM (#34947962)
Several counterexamples were listed in the article.