History is not trivia here — it explains why Node.js is shaped the way it is. The event loop, the obsession with non-blocking I/O, the CommonJS module system, the npm registry, and even the modern features arriving today all make more sense once you know the problems and arguments that produced them.

In 2009, Ryan Dahl was frustrated by how web servers handled concurrency. The dominant model — one thread (or process) per connection, as in Apache and classic PHP — wasted memory and CPU because each connection held a whole thread hostage even while it was just waiting on I/O. He often cited a concrete example: a file-upload progress bar. The browser couldn't easily track upload progress because the server was blocked while receiving the file, unable to report status.

Dahl's insight was to use a single-threaded event loop with non-blocking I/O — the same architecture that made the Nginx web server scale far better than Apache under high concurrency. He needed a language with first-class functions, closures, and an event-driven culture to make callback-based async natural. JavaScript fit perfectly: it already worked this way in the browser, had no built-in I/O library to conflict with (a blank slate), and Google had just released the astonishingly fast V8 engine. Node.js combined V8 with an I/O library (originally libev/libeio, later unified as libuv).

A runtime is only as valuable as the code available for it. npm (2010) gave Node a central registry and a trivially simple way to publish and install packages. Network effects took over: more packages attracted more developers, who published more packages. Today npm is the largest software registry in existence (over two million packages). Much of Node's dominance is really npm's dominance — and the modern concern with supply-chain security is the shadow side of that same success.

By 2014, Node was controlled by a single company (Joyent), and many core contributors were unhappy with the slow release pace and closed decision-making. They forked the project into io.js, which shipped newer V8 versions and moved faster. The pressure worked: in 2015 the two reunited under the independent Node.js Foundation, adopting an open governance model and a predictable release schedule.

In a now-famous 2018 talk, "10 Things I Regret About Node.js," Dahl criticized several early decisions:

He built Deno to explore the alternatives: secure-by-default permissions, built-in TypeScript, URL-based imports, and web-standard APIs. Rather than killing Node, Deno (and later Bun) pushed it to evolve. Modern Node now has native ES Modules, a permission model, a built-in test runner, native fetch, and --watch — which is why today's Node feels very different from the Node of 2015.