[schimmy_changa]

This is a bit of a hyperbolic title and post, but it does seem like a real issue that the Golang devs should address. Letting the socket do its thing seems like the right way to go, although I'm not an expert in networking.

Any ideas from the devs or other networking experts here in HN?

[blibble]

I suspect the current behaviour will have to stay as it is because the universe of stuff that could break as a result of changing it is completely unknowable

[LeoNatan25]

So it’s not hyperbolic, and actually describes things as they are?

[joemi]

Calling it "evil" is hyperbolic.

[withinboredom]

At this point, this problem has caused me dozens if not hundreds of hours of waiting on slow transfers. It is evil. Maybe I should disable all my neighbor’s routers or convince the local authorities to open more 5Ghz spectrum… but it is what it is.

[akdor1154]

I dunno.. I am not a networking expert by any stretch, but it does seem consistent with Golang's philosophy that devs should have a deep understanding of the various levels of the stack they're working in.

Though TFA does make a fair point that in reality this doesn't happen, and there is slow software abound as a result.