News for hackers. Stuff that matters.
Re:It's Always TCP_nodelay by immibis on Tuesday December 23, 2025 @06:39AM (#46364493)
So to be clear, you believe every program that outputs a bulk stream to stdout should be written to check if stdout is a socket and enable Nagle's algorithm if so? That's not just busywork - it's also an abstraction violation. By explicitly turning off Nagle's, you specify that you understand TCP performance and don't need the abstraction, and this is a reasonable way to do things. Imagine if the kernel pinned threads to cores by default and you had to ask to unpin them...
Re:It's Always TCP_nodelay by rocqua on Tuesday December 23, 2025 @08:14AM (#46365083)
No, the program should take care to enable TCP_NODELAY when creating the socket. If the program gets passed a FD from outside it's on the outside program to ensure this. If somehow the program very often gets outside FDs from an oblivious source that could be a TCP socket, then it might indeed have to manually check if it really wants Nagle's algorithm.
Re:It's Always TCP_nodelay by mort96 on Wednesday December 24, 2025 @08:13AM (#46375281)
> That's not just busywork - it's also an abstraction violation.

You used AI to write this didn't you? Your sentence structure is not just tedious - it's a dead give-away.

Re:It's Always TCP_nodelay by immibis on Wednesday December 24, 2025 @10:26PM (#46381806)
No, I did not. Am I now forbidden from using sentence structures that AI has also used? That's not just stupid - it's insane. You know that's not even an em-dash, right?