Golang disables Nagle's Algorithm by default
> I would absolutely love to discover the original code review for this and why this was chosen as a default. If the PRs from 2011 are any indication, it was probably to get unit tests to pass faster. If you know why this is the default, I’d love to hear about it!<p>Please hold while I pick my fallen jaw up off the floor.<p>The parents of the Internet work at Google.  How could this defect make it to production and live for 12+ years in the wild?  I guess nothing fixes itself, but this shatters the myth of Google(r) superiority.  It turns out people are universally entities comprised of sloppy, error-prone wetware.<p>At the very least there should be a comment in caps and in the documentation describing why this default was chosen and in what circumstances it's ill-advised.  I'm not claiming to be remarkably exceptional and even I bundle such information on the first pass when writing the initial code (my rule: to ensure a good future, any unusual or non-standard defaults deserve at least a minimal explanation) (Full-Disclosure: I was rejected after round 1 of Google code screens 3 times, though have been hired to other FAANG/like companies).<p>Yeesh.<p>p.s. Be sure to brace yourself before reading <a href="https://news.ycombinator.com/item?id=34179426#34180015" rel="nofollow">https://news.ycombinator.com/item?id=34179426#34180015</a>