The Web Became Programmable: From Hypertext to JavaScript
The Web began as a system for linked documents. Within a few years, code had moved into the browser and the document surface was becoming an application platform.
When Tim Berners-Lee proposed the World Wide Web at CERN in 1989, the central problem was information sharing. Researchers needed a flexible way to link documents across incompatible systems.[1] By the end of 1990, CERN had the first web server and browser running; the first website explained the Web itself.[2]
The original Web was already programmable in the broad sense that servers generated and delivered information through protocols. But the decisive cultural shift came when programming moved into the browser.
Open distribution mattered as much as invention
CERN’s 1993 decision to release the World Wide Web software into the public domain helped maximize adoption.[1] This made the Web a permissionless substrate on which browsers, servers, languages, and businesses could compete without one organization controlling the core idea.
That openness is part of why the Web became an unusually fertile programming environment. A page could be viewed anywhere; later, scripts could make it behave differently everywhere.
JavaScript turned the document into a runtime
JavaScript first appeared in Netscape Navigator 2.0. The ECMAScript specification records that Brendan Eich invented the language at Netscape and that standardization work began in November 1996, with the first ECMA-262 edition adopted in June 1997.[3]
This changed the browser’s role. HTML described structure, CSS would increasingly control presentation, and JavaScript could react to users, manipulate the document, validate input, request data, and eventually host entire applications.
Standardization made competition survivable
The browser wars were messy, but a standardized language created a shared target. Ecma notes that JavaScript and Microsoft’s JScript were among the originating technologies brought under the ECMAScript standard.[3] The language could evolve through a multi-implementer process rather than remain a proprietary feature of one browser.
That is a recurring lesson in coding history: successful platforms often separate implementation competition from interface agreement. Standards give programmers something stable enough to build against.
The browser swallowed the application stack
Over the next decades, the Web accumulated APIs for graphics, audio, storage, real-time communication, devices, cryptography, workers, modules, and more. JavaScript runtimes also escaped the browser and entered servers, build systems, desktop shells, and tooling.
What began as linked documents became a universal software distribution surface. You could send someone a URL and deliver not just information but an executable interface.
The Web made code public by default
Web development also normalized a strange cultural fact: much client-side code is delivered directly to the user’s machine. Source maps, developer tools, network inspectors, and browser consoles made the runtime unusually observable. Millions learned programming by viewing source, copying snippets, and changing pages live.
The programmable Web therefore sits at the intersection of open standards, distribution, language design, and culture. It turned the document into a software surface—and made publishing code inseparable from publishing experiences.
Works Cited
- 01CERN — The birth of the Web home.cern
- 02CERN — A short history of the Web home.cern
- 03Ecma International — ECMAScript Language Specification, historical introduction 262.ecma-international.org
- 04Ecma International — ECMA-262 20th anniversary and early standardization history ecma-international.org
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.