News for hackers. Stuff that matters.

A comment on Toward Go 2.

Re:Toward Go 2 by notjack on Thursday July 13, 2017 @03:55PM (#14764622)
> We did what we always do when there's a problem without a clear solution: we waited. Waiting gives us more time to add experience and understanding of the problem and also more time to find a good solution. In this case, waiting added to our understanding of the significance of the problem, in the form of a thankfully minor outage at Cloudflare. Their Go code timed DNS requests during the end-of-2016 leap second as taking around negative 990 milliseconds, which caused simultaneous panics across their servers, breaking 0.2% of DNS queries at peak.

This is absurd. Waiting to fix a known language design issue until a production outage of a major customer is a failure of process, not an achievement. The fact that the post presents this as a positive aspect of Go's development process is beyond comprehension to me.

[ Parent | on HN ]
Re:Toward Go 2 by TazeTSchnitzel on Thursday July 13, 2017 @06:14PM (#14765770)
They did the same thing with adding a “round” function. As a result, there are myriad implementations of round() in the wild in Go, and almost every single one is broken in several ways.
[ Parent | on HN ]
Re:Toward Go 2 by 43224gg252 on Thursday July 13, 2017 @06:15PM (#14765784)
It's not absurd. This methodology may not be best for everyone, but imo it's best for the language its self, and seeing as Go is one of todays fastest growing languages the developers must be doing something right.
[ Parent | on HN ]