23 ms·
How can you call it a defect when it might have been a deliberate decision? Your whole post sounds like you're upset Google didn't hire you lmao
by tourist2d 4y ago
How can you call it a defect when it might have been a deliberate decision? Your whole post sounds like you're upset Google didn't hire you lmao
- fsdjkflsjfsoij 4y agoThe entire post is embarrassing and makes me think that Google made the correct decision. Also, it seems that people that want to change the default behaviour can simply use the TCPConn.SetNoDelay function.
- metadat 4y agoDecisions deserve documentation (because a footgun warning is preferable to spontaneous unintended penetration).
- geodel 4y agoHuh, really? There is public API to change behavior, thats about it. There maybe a million page documentation by now if every decision needed a documentation.
- metadat 4y agoAs the amount of confusion and back-and-forth in this story thread proves, such topics deserve more attention rather than being lumped in alongside less consequential matters. Ideally the goal is to spread the knowledge and expertise to as many humans as possible by making it accessible.
- parasubvert 4y agoThe only thing this story thread proves is that young folks aren’t being taught basic networking or distributed systems functionality and history. TCP options and disabling Nagle’s algorithm was a topic you learn when introduced to RPCs, maybe in 3rd or 4th year, at least in the 90s.
- loeg 4y agoIt is documented. https://pkg.go.dev/net#TCPConn.SetNoDelay https://pkg.go.dev/net#TCPConn.SetNoDelay > The default is true (no delay), meaning that data is sent as soon as possible after a Write.