In 2013, a software engineer named Gary Bernhardt gave a talk at a tech conference called Strange Loop. He called it "The Birth and Death of JavaScript." The talk was funny — it was written as a pretend speech from some future time, describing how JavaScript rose to power and then got replaced by something else. More than a decade later, people are still watching and sharing it.

JavaScript is the programming language that runs in web browsers. For most of its history, that is where it stayed. But by 2013, programmers were already experimenting with using JavaScript on servers and in other places too. Bernhardt's talk imagined this trend going much further — into operating systems and hardware, into places that seemed wild at the time.

He also predicted something called WebAssembly would eventually take over. In 2013, WebAssembly did not officially exist yet. It was just an idea. But Bernhardt's core point was not really about WebAssembly specifically — it was about how programming languages rise and fall. He was arguing that something lower-level and more portable would eventually route around JavaScript rather than replace it entirely.

Bernhardt gave the same talk twice, to two very different crowds. The first audience at Strange Loop were systems programmers and language experts. The second, at a conference called PyCon, were Python programmers. The fact that he gave the same talk to both groups suggests he was talking about something bigger than JavaScript alone — something about how technology ecosystems change.

WebAssembly has since become real. In 2019, it became an official web standard. Today, major companies use it. Figma, a design tool, uses WebAssembly to make its software faster. Cloudflare uses it to run code across its servers. And system interfaces are being built to let WebAssembly run more places, just as Bernhardt imagined.

JavaScript never died. In fact, it runs in more places than ever. But Bernhardt got the bigger picture right: JavaScript and WebAssembly now coexist exactly as his fictional future described. JavaScript is the familiar layer on top, and WebAssembly is the faster, more portable layer underneath.

Why does a decade-old talk keep resurfacing? Because it was not really a prediction about the future — it was an argument about why things change the way they do. Predictions can be wrong. But arguments about human behavior and competition tend to hold up. Bernhardt's talk works because he was reasoning about the forces that shape technology adoption, and those forces have not changed.