Netscape

The Story

In the spring of 1993, a 22-year-old undergraduate named Marc Andreessen and a staff member named Eric Bina at the National Center for Supercomputing Applications (NCSA) at the University of Illinois released Mosaic — a graphical web browser that could display images inline with text. The web had existed since Tim Berners-Lee's work at CERN in 1991, but it had been text-based, arcane, and confined largely to academic users. Mosaic made it visual. For the first time, you could see pictures on a web page without downloading them separately. The effect was electric. Mosaic's user base grew from nothing to millions within a year.

Andreessen graduated and moved to California, where he met Jim Clark — the founder of Silicon Graphics, a man with capital, ambition, and a conviction that the web was about to become very large. In April 1994, they founded Mosaic Communications Corporation, hired most of the original Mosaic team away from NCSA, and set about building a better browser from scratch. NCSA objected to the name. The company became Netscape Communications Corporation. The browser became Netscape Navigator.

Navigator 1.0 shipped in December 1994. It was faster than Mosaic, more stable, and — crucially — it shipped with a feature that made commercial use of the web possible: Secure Sockets Layer. SSL, designed by Netscape engineer Taher Elgamal, provided encrypted communication between browser and server. Before SSL, everything transmitted over the web — including any credit card number you typed into a form — traveled in plaintext. SSL gave the web a security layer. Without it, e-commerce could not have existed. The padlock icon in your browser's address bar, the https:// prefix, the entire infrastructure of encrypted web communication — it started at Netscape.

Navigator also shipped with cookies — small pieces of data that a server could store in the browser and retrieve on subsequent requests. This sounds mundane. It was architecturally revolutionary. HTTP is stateless: each request is independent, with no memory of previous requests. Cookies gave the web state. They made it possible to log in to a site and stay logged in. They made shopping carts possible. They made personalization possible. They made sessions possible. Lou Montulli, who implemented cookies at Netscape, solved the web's memory problem with a mechanism so simple and effective that it's still the primary state-management tool in web applications thirty years later.

And then there was JavaScript.

In May 1995, Netscape recruited Brendan Eich with the promise that he could implement Scheme — a clean, elegant Lisp dialect — in the browser. What actually happened was dictated by corporate politics and a punishing deadline. Netscape had a partnership with Sun Microsystems, which wanted its Java language promoted in the browser. Management wanted a scripting language that looked like Java (curly braces, C-style syntax) but was simpler — a "little brother" language for web designers who wouldn't write full Java applets. Eich had ten days.

In ten days, Brendan Eich created the language that would become the most widely deployed programming language in human history. It was called Mocha internally, shipped as LiveScript, and was renamed JavaScript as part of the Sun marketing deal — a naming decision that has confused beginners for three decades. The language Eich produced in that ten-day sprint was remarkable, flawed, and inescapable. It had first-class functions, closures, and prototypal inheritance — ideas from Scheme and Self that were genuinely ahead of their time. It also had typeof null === 'object' (a bug in the original implementation that could never be fixed without breaking the web), aggressive type coercion that produces results like [] + [] === "" and [] + {} === "[object Object]", and the == operator whose behavior is governed by an abstract equality comparison algorithm complex enough to require its own flowchart. These weren't design choices. They were the artifacts of a ten-day implementation timeline imposed by business requirements.

Netscape Navigator dominated the early web. By 1996, it held over 80% of the browser market. Netscape's IPO on August 9, 1995 — the stock opened at $28, hit $75 on the first day, and closed at $58.25 — is widely cited as the event that ignited the dot-com boom. A company with less than $50 million in revenue was valued at nearly $3 billion. The web was worth money. The gold rush began.

Microsoft noticed.

Internet Explorer 1.0 shipped in August 1995, based on licensed Mosaic code. It was late, crude, and irrelevant. IE 2.0 was better. IE 3.0, shipping in 1996, achieved rough feature parity with Navigator. Then Microsoft made the move that would define the browser wars and trigger the largest antitrust case in tech history: they bundled Internet Explorer with Windows.

The bundling was devastating. Netscape charged for Navigator (though it was free for students and non-commercial users). Microsoft gave IE away for free and embedded it in the operating system that ran on 90% of the world's personal computers. Netscape's market share collapsed — from over 80% in 1996 to under 30% by 1999. It wasn't that IE was better (it was often worse, particularly IE's non-standard implementations of CSS and JavaScript). It was that IE was already there, on every Windows machine, and Netscape wasn't.

The U.S. Department of Justice filed its antitrust case against Microsoft in May 1998, alleging that bundling IE with Windows constituted illegal monopoly maintenance. The case dragged on for years. Microsoft was found to have violated antitrust law. The remedy — a consent decree requiring Microsoft to share APIs with third parties — came too late to save Netscape.

AOL acquired Netscape in November 1998 for $4.2 billion. By then, the company's most consequential act was already underway. On March 31, 1998, Netscape had released the source code of its browser under an open-source license, launching the Mozilla project. The code was a mess — years of competitive feature additions had left Netscape Communicator's codebase nearly unworkable. The Mozilla team eventually scrapped most of it and rebuilt from the ground up. The result, years later, was Firefox, which launched in November 2004 and broke IE's monopoly from below, reaching 30% market share by 2010. Mozilla also produced the Gecko rendering engine, Thunderbird, and — through the standardization work it drove — helped establish the web standards that modern browsers are built on.

AOL shut down the Netscape browser on February 1, 2008. The Netscape brand lingered as a web portal for a few more years. The company that had started the browser era, created the language of the web, and given the web encryption was gone.

Why They're in the Hall

Netscape is a Pioneer and a Builder — and their placement is unambiguously in the Hall of Fame, because the things they built in a four-year window from 1994 to 1998 are still running the world.

JavaScript: There is no honest way to discuss the modern web without starting here. JavaScript is the language of the browser, the language of Node.js, the language of React, Angular, Vue, Svelte, and every frontend framework. It's in server-side applications, mobile apps (React Native), desktop apps (Electron), serverless functions, and embedded systems. The npm registry contains over two million packages. Every web-era exhibit in TechnicalDepth — every injection vulnerability, every client-side bug, every DOM manipulation gone wrong — executes in a JavaScript runtime that descends from Brendan Eich's ten-day prototype.

The ten-day timeline left scars that generate bugs to this day. Type coercion produces unexpected behavior that even experienced developers stumble over. The difference between == and === is a source of defects in every JavaScript codebase. this binding rules are complex enough to warrant their own chapter in any JavaScript textbook. typeof null === 'object' is a bug from the original implementation — the null value was represented internally with a type tag of zero, which was also the tag for objects — and it can never be fixed because fixing it would break existing code. These aren't theoretical concerns. They're in production code, on every website, right now.

SSL/TLS: Netscape's Secure Sockets Layer became Transport Layer Security, which became the encryption layer for functionally all secure communication on the internet. Every HTTPS connection, every encrypted API call, every secure WebSocket — they run on a protocol lineage that began at Netscape. The padlock icon, the certificate chain, the handshake that negotiates cipher suites between client and server — this infrastructure is so fundamental that its absence (plain HTTP) is now treated as a security warning by browsers. Netscape didn't just add encryption to the web. They made encryption the default expectation for web communication.

Cookies: Netscape's solution to HTTP's statelessness enabled sessions, which enabled authentication, which enabled personalized web applications, which enabled the modern web. Cookies also enabled tracking — third-party cookies became the backbone of the advertising surveillance economy, and a persistent vector for security vulnerabilities. Cross-site request forgery (CSRF) exploits the fact that browsers automatically attach cookies to requests. Session hijacking exploits the fact that session state is tied to a cookie value. The SameSite, Secure, and HttpOnly cookie attributes exist because the original cookie specification, designed for functionality in 1994, didn't anticipate how cookies would be exploited in an adversarial web. Netscape's invention gave the web memory. That memory turned out to be exploitable.

Mozilla and open source: Netscape's decision to release their browser source code — made in desperation as IE's bundling strategy destroyed their market share — was one of the most consequential acts of open-source release in software history. The Mozilla project that emerged produced Firefox, which broke IE's monopoly and forced Microsoft to compete on standards compliance. The Gecko engine drove web standards forward. The Mozilla Foundation's advocacy for an open web — open standards, user privacy, interoperability — established institutional counterweight to the platform monopolies that would dominate the following decades.

Netscape was killed by a monopoly, not by its own failures. Their technology was sound, their inventions were foundational, and their contributions to the open web — both through their products and through their open-source release — shaped the infrastructure that every web application runs on today. The browser war they lost led to the antitrust case that constrained Microsoft, which created the competitive space for Google, which created Chrome, which now holds the dominant market position that IE once held. The cycle continues. But the protocols, the language, and the architectural patterns that Netscape introduced between 1994 and 1998 remain the foundation.