News for hackers. Stuff that matters.
Re:Telemetry in the Go Toolchain by cube2222 on Wednesday February 08, 2023 @03:22PM (#34714391)
All this boils down to "an unskilled engineer will misinterpret data even if they have it". I'll assume the Go team knows what they're doing, based on their track record so far.

There's a lot of very simple questions you can answer very reliably, too, like "what proportion of the users are still using a certain compatibility flag".

Re:Telemetry in the Go Toolchain by marginalia_nu on Wednesday February 08, 2023 @03:27PM (#34714480)
My point is that scientists whose job is to interpret data and construct experiments gets this wrong on a regular basis, despite years of training in constructing experiments and interpreting data, despite peer review, despite staking their career and reputation on not making these kinds of mistakes. They still happen! A lot!

Interpreting data is very hard.

Re:Telemetry in the Go Toolchain by masklinn on Wednesday February 08, 2023 @04:44PM (#34715715)
> I'll assume the Go team knows what they're doing, based on their track record so far.

Funny, I’d assume the exact opposite. After all much of the understanding of privacy and statistics at scale was developed after 1980.

Re:Telemetry in the Go Toolchain by philosopher1234 on Wednesday February 08, 2023 @08:14PM (#34718360)
Normally Hacker News is ruthless with stupid comments like this, but some sort of unexamined feelings of inadequacy make Go devs a fair target. I hate this attitude.
Re:Telemetry in the Go Toolchain by remram on Wednesday February 08, 2023 @08:27PM (#34718475)
Go is actually well known for dubious choices they reverted later, like not using libc, their weird major version scheme, or the absence of generics. There's a good record of charging ahead against the popular wisdom and being proven wrong.