Is it? You probably feel that way from knowing how TCP works. But it would be quite straightforward to make it true with a slightly modified version of TCP (that acknowledges all packets, rather than every second one) by having send() block until it receives back the ACK from the receiver. (Yeah this would kill transmission rates, but it would function!) And furthermore, while it would be a terrible idea, the ACK could even be delayed until the end application makes the recv() call for the packet.
To somebody not familiar with the details (and why this would be a terrible tradeoff), something along those lines would be entirely plausible.
Actually I think it's even a mistake to call TCP reliable. It's best-effort, and allows you to detect disconnects. That's all it does because that's all it can do.
No, I knew that from yanking out a network cable long before I even knew what TCP was.
There are many statements that fit into the category of "obvious once stated, but not obvious if you didn't consider the distinction to begin with".
Uhh, that's 100% obvious. That's why it's not taught.
Of course, I've also goofed on things that are obvious to other people. But, com'on, TCP isn't magic.