The BSD socket API arrived in 4.2BSD in 1983, giving C programmers a uniform interface for network communication. Its designers could not have anticipated that their creation would still be the foundation of essentially all network programming forty-plus years later — on Linux, macOS, Windows, embedded RTOS firmware, and everything in between. The API’s quirks are legendary: the byzantine dance of socket(), bind(), listen(), accept(), and the remarkable fact that send() might not actually send everything you asked it to. Every networking tutorial written since 1990 contains the same footnote about checking return values and handling partial sends. Every junior developer ignores it. Every senior developer has the scar tissue to prove it.
