Every time an AI answer types itself out on your screen, word by word, you’re watching a nineteen-year-old technology finally get a job it’s actually good at.
Server-Sent Events. Concept showed up in 2004. Opera shipped the first real implementation in 2006. Then… nothing, for most of a decade. WebSockets came along around the same time and ate all the oxygen in the room, because “full-duplex, bidirectional, real-time” sounds like something you’d put in a job posting, and SSE sounded like the tech equivalent of a beige sedan nobody test-drives.
Here’s what nobody tells you: most apps never needed full-duplex. They needed the server to talk and the client to shut up and listen. Stock tickers. News feeds. And now, every AI response you’ve ever watched stream in. The whole thing is maybe ten lines:
header("Content-Type: text/event-stream");
header("Cache-Control: no-cache");
echo "data: " . $chunk . "\n\n";
flush();
That’s it. No new protocol. No handshake ceremony. It just sits there, over plain HTTP, being unglamorous and correct — and it even reconnects itself for free if the connection drops. Turns out the thing that makes Claude feel alive instead of a spinning wheel of death is the least exciting technology in the whole stack.
Then I hit Session IDs in MCP’s transport layer, and something clicked that had nothing to do with web dev. Tracking a conversation over a connection that only talks in one direction isn’t a new problem. That’s PCI. That’s PCI-Express. That’s the front-side bus. Hardware engineers were solving “which packet belongs to which conversation” before most of today’s framework authors were in school.
Nobody in this industry invented something new. Somebody found an old, solved problem wearing a different jacket, and called it a breakthrough.
And look — I’ve read something like 20,000 job listings over the last two and a half years. This is the same move I see in half of them. “5 years of experience required” for a framework that’s been public for two. Somebody dusted off an old assumption — more years automatically means more skill — slapped it on something brand new, and never checked whether the math even works. Old idea. New paint. Nobody doing the arithmetic.
That’s most of what passes for “cutting edge” right now, if you actually go looking. In tech stacks. In job postings. Same trick, different jacket.