The History of the Web Browser and the Browser Wars
A comprehensive history of the web browser, from the early hypertext concepts at CERN to the intense competition of the Browser Wars and the modern platform era dominated by a few major engines.
19 posts about web development
A comprehensive history of the web browser, from the early hypertext concepts at CERN to the intense competition of the Browser Wars and the modern platform era dominated by a few major engines.
The web was built to forget you between every request, so every login system you have ever used is a clever workaround for that fact. Here is how cookies, sessions, tokens, and OAuth actually fit together, and where each one bites.
From subroutine libraries to CORBA and SOAP, then REST, GraphQL, and gRPC, with each generation fighting the last one's ceremony.
For much of the web's history, we built page layouts with tools that were never designed for the job. The story of CSS layout is the slow arrival of tools that actually fit the problem, and why the old hacks were not anyone's fault.
You type an address, press enter, and a page appears in under a second. In that moment your computer talks to a dozen machines across the planet. Here is the whole journey, step by step, and where the time actually goes.
Where a web page gets built, on the server or in the browser, has swung back and forth for twenty years. Each swing solved the previous era's pain and created new pain of its own. Here is the full arc, and why it is not going in circles.
The fastest request is the one you never have to make. Web caching is the layered system that avoids repeated work, and it hides one of the genuinely hard problems in computing. Here is how it holds together, and how it quietly leaks private data when it goes wrong.
SQL is more than fifty years old, has been declared obsolete more than once, and still runs the data layer of nearly every web application. Here is where it came from, the rival language it beat, and why nothing has managed to replace it.
Go was a reaction. Three veteran engineers at Google, frustrated by slow builds and growing complexity, built a language that left features out on purpose. That restraint made it the language of modern cloud infrastructure.
For most of the web's life, the browser had one native language. WebAssembly changed that by giving the browser a fast, portable compile target that any language can reach, and it is quietly becoming a runtime far beyond the browser.
C# was born out of a lawsuit. Blocked from extending Java, Microsoft built its own modern language, had it standardized so no one could call it a cage, and spent two decades turning it into a fast, open, cross-platform tool.
PHP was never meant to be a programming language. It started as a few tools one developer wrote to track visits to his resume, survived an existential threat from Facebook, and still runs a large share of the web. Here is how.
Downloading a page and showing it are two different jobs. The second one, turning HTML and CSS into pixels, is where most of the waiting happens. Here is how a browser does it and why some resources block the whole thing.
Most languages optimize for the machine or the problem. Ruby set out to optimize for the person writing the code. That unusual goal, plus one framework, turned it into the language behind a generation of startups.
The padlock in your address bar is the visible end of a quiet negotiation involving two kinds of cryptography, a signed certificate, and a chain of trust that reaches back to your operating system. Here is what is really happening, including the part everyone gets slightly wrong.
Java was built to run on television set-top boxes. That market never arrived, but the idea underneath it, code that runs anywhere without changes, made Java the language of enterprise software and Android. Here is the story.
A comprehensive overview of Netlify, the web development platform known for pioneering the Jamstack architecture, detailing its history, products, business model, and competitive landscape for a technical audience.
JavaScript's flexibility is a gift on a small page and a liability in a large codebase. TypeScript was Microsoft's answer: keep the language, add a type system on top. Here is where it came from and why it won when every earlier attempt failed.
A detailed comparison of polling, Server-Sent Events, and WebSockets, explaining their mechanisms, tradeoffs, and ideal use cases for building real-time web applications.