News for hackers. Stuff that matters.

A comment on Golang is evil on shitty networks. Parent comment

Re:Golang is evil on shitty networks by SomaticPirate on Thursday December 29, 2022 @07:20PM (#34179982)
Go’s choice to default to its own TCP/IP implementation has bitten me personally to the level of requiring a machine restart.

The Go IPv6 DNS resolution on MacOS can cause all DNS requests on the system to begin to fail until a restart.

https://github.com/golang/go/issues/52839

[ Parent | on HN ]
Re:Golang is evil on shitty networks by alecthomas on Thursday December 29, 2022 @10:17PM (#34181391)
Not to understate the impact of the bug, but this is not the default for Go. It is used if CGo is disabled, as the issue you linked to describes.
[ Parent | on HN ]
Re:Golang is evil on shitty networks by jen20 on Friday December 30, 2022 @08:01AM (#34184609)
That is the default for Go if cross-compiled, however, and most software compiled on a CI server is cross-compiled to Darwin.

Fortunately Go 1.20 fixes this, using the system resolved even without CGo on Darwin platforms [1].

[1]: https://go-review.googlesource.com/c/go/+/446178

[ Parent | on HN ]
Re:Golang is evil on shitty networks by EdiX on Friday December 30, 2022 @02:39AM (#34182833)
The OS network stack is crashing and this is Go's fault? Is Go holding the network stack wrong?
[ Parent | on HN ]