Architecture · 1983–now · Foundations
TCP/IP
The network stack that won. Every "revolutionary" protocol still rides these packets.
TCP/IP won by being good enough, debuggable, and incrementally deployable — not by committee perfection. Alternatives arrived with better slides and worse adoption paths. The internet is the proof that boring protocols outlive elegant ones.
Context
Machines learn to share a language
This era built the substrate. Process models, pipes, files-as-interfaces, and relational algebra were not fashion — they were constraints that happened to scale. C and Unix made portability a real goal; SQL made data queryable without rewriting the world. Later decades mostly decorate or redistribute these ideas. When something from this era still looks “boring,” that usually means it won.
Compare with
Related
Platform · 1991–now
HTTP / HTTPS
The application protocol of the internet. HTTP/2 and HTTP/3 are evolutions, not replacements.
Platform · 1971–now
Unix / POSIX
Process model, pipes, and files-as-interfaces. Linux and macOS still speak this dialect every day.
Architecture · 2015–now
gRPC
Binary RPC with contracts. Fast internal glue that should never face the public internet without a gateway.