The 127-Slide Deck That Launched a War: How Larry Page Unveiled Google Chrome While Microsoft's CEO Was on Vacation — And Killed Internet Explorer in 6 Years

The Comic Book That Broke the Internet

It was August 31, 2008, 11:47 PM Pacific Time. Philipp Lenssen, a German blogger running a niche tech site called Google Blogoscoped, received an email from someone at Google. Attached was a PDF. Not a press release. Not an invitation. A 38-page comic book.

Lenssen opened it. On page one, a cartoon version of Sundar Pichai sat in a conference room explaining why browsers were "fundamentally broken." By page three, there were diagrams of process isolation and V8 JavaScript engines. By page ten, it was clear: Google was launching a web browser.

The comic was supposed to embargo until morning. Lenssen published it immediately.

By 6 AM, the tech world had melted down. Microsoft's Internet Explorer team woke up to headlines. Mozilla's CEO called an emergency meeting. And Larry Page — Google's co-founder who rarely did product launches — was about to walk onstage in San Francisco to declare war on the entire web.

The Crisis Nobody Saw Coming

Rewind to 2006. Google was printing money from search ads. Gmail was growing. Google Maps had just launched. But inside the Googleplex, a quiet crisis was brewing.

Web apps were dying in Internet Explorer.

Gmail would freeze for 10 seconds loading your inbox. Google Maps would choke rendering tiles. Google Docs — Google's bet on replacing Microsoft Office — was borderline unusable in IE6, which still commanded 60% market share.

The problem wasn't just Microsoft's browser. Every browser was built for the web of 1998 — static HTML pages with a sprinkle of JavaScript. But Google was trying to build applications that lived in the browser. Gmail wasn't a webpage. It was a desktop email client rendered in JavaScript.

And JavaScript engines in 2006 were catastrophically slow.

Lars Bak, a Danish engineer famous for building the fastest Java virtual machine in the world, joined Google in 2006 with one mission: make JavaScript 10x faster. He assembled a team in a secret building in Aarhus, Denmark. No name. No logo. Just a mandate: build a JavaScript engine from scratch.

They called it V8.

But Bak had a problem. Even with the world's fastest JavaScript engine, Chrome would still be slow if it ran in someone else's browser. Firefox was open-source but controlled by Mozilla. Safari was Apple's. Internet Explorer was Microsoft's, and they'd just spent a decade in antitrust court for bundling it with Windows.

Sundar Pichai — then a rising VP who'd joined Google three years earlier from McKinsey — walked into Larry Page's office with a nuclear option: build our own browser.

Page's response: "Why?"

Pichai's answer changed everything: "Because if we don't control the platform, we'll never control our destiny."

The Project That Couldn't Exist

Google's leadership was split. Sergey Brin was skeptical. Eric Schmidt, the CEO, thought it was a distraction. Marissa Mayer — then VP of Search Products — argued it would alienate Mozilla, whose CEO was on Google's board and whose browser sent billions in search traffic.

But Page saw something bigger. The web was becoming the operating system. Whoever controlled the browser would control computing for the next 20 years.

He gave Pichai the green light — with two conditions:

1. Build it in total secrecy
2. Make it so fast that nobody could ignore it

Pichai assembled a team of 20 engineers in 2006. They worked out of a nondescript building in Mountain View. No Google logo. The project had a codename: "The Chrome Project." The joke was that they wanted to reduce browser "chrome" — the UI clutter — to almost nothing.

The technical ambition was insane. They weren't just building a browser. They were rethinking what a browser was.

The Big Bets:

1. Multi-Process Architecture
Every tab would run in its own process, isolated from the others. If one tab crashed, the rest would survive. In 2006, this was heresy. Firefox, Safari, IE — they all ran in a single process. One bad webpage could kill your entire browser.

Ben Goodger, the engineer who'd built Firefox 1.0 before joining Google, led the architecture. He borrowed ideas from operating systems: process isolation, sandboxing, privilege separation. Each tab was a prisoner in its own cell.

2. V8 Engine
Lars Bak's team shipped a JavaScript engine that was 10-100x faster than anything else. They used hidden classes (borrowed from Smalltalk), inline caching, and a just-in-time compiler that turned JavaScript into machine code on the fly.

When they benchmarked it against Firefox's SpiderMonkey and Safari's JavaScriptCore, the results were absurd. Gmail loaded in 2 seconds instead of 20. Google Maps rendered instantly.

3. The Omnibox
Ditch the separate search box. The address bar is the search box. Type a URL, it goes there. Type a question, it searches Google. In 2008, this was radical. Now it's how every browser works.

4. Security as a Feature
Every process ran in a sandbox. Exploiting a webpage couldn't touch your OS. Built-in phishing and malware detection. Auto-updates that happened silently in the background (another heresy — users hated forced updates in 2008).

By summer 2008, they had a working browser. It was fast. It was stable. And it was about to upend the entire industry.

The Launch That Changed Everything

September 1, 2008. Larry Page walked onto a small stage at a theater in San Francisco. No Jobsian theatrics. No "one more thing." Just 127 slides and a mission to explain why Google — a search company — was launching a browser.

Page opened with the problem: "The web has evolved. Browsers haven't."

He showed a slide of Gmail's JavaScript code: 1.2 million lines. Then a slide of the average webpage in 2000: 10KB of HTML and 2KB of JavaScript. The gap was unbridgeable.

Then Sundar Pichai took over. He demoed Chrome loading Gmail in 1.8 seconds. Then he opened 20 tabs — each playing a different YouTube video. No lag. No crashes. He closed 15 tabs. The browser didn't blink.

Then he did something nobody expected: he crashed a tab on purpose. Went to a malicious webpage. The tab turned gray. A sad face appeared. The rest of the browser kept running.

The audience gasped.

Ben Goodger explained the multi-process architecture. Lars Bak walked through V8's JIT compiler. They showed the Omnibox. They showed the minimalist UI — no menu bar, no status bar, just a tab strip and an address bar.

The last slide was a single sentence:

"We're releasing Chrome as open-source. Today."

The code — all of it, including V8 — was published on chromium.org that afternoon under a BSD license. Competitors could use it. Fork it. Study it. Google didn't care.

Because the browser was just the beginning.

The War That Followed

Week 1:
Chrome hit 1% market share in 3 days. Firefox users were furious — Google had poached Mozilla's best engineers and declared war. Mozilla's CEO, Mitchell Baker, issued a terse statement: "We welcome competition."

Microsoft said nothing. IE8 was months from shipping. Steve Ballmer was on vacation.

Month 3:
Chrome hit 5% market share. Microsoft finally responded: they started rebuilding IE with a new JavaScript engine (Chakra) inspired by V8. Too late.

Year 1:
Chrome hit 10%. Mozilla adopted parts of Chrome's architecture for Firefox 4. Apple pulled V8's ideas into JavaScriptCore (they called it SquirrelFish Extreme, because Apple).

Year 3 (2011):
Chrome overtook Firefox to become the #2 browser globally.

Year 6 (2014):
Chrome overtook Internet Explorer to become the #1 browser on Earth — 45% market share and climbing. Microsoft, in a stunning reversal, announced they were killing IE and building a new browser (Edge). It would be based on Chromium. Google's open-source project.

The war was over. Google had won.

The Turning Point: Why Chrome Mattered

Chrome didn't just win the browser wars. It redefined what software could do.

Because V8 was so fast, web apps became viable. Spotify launched a web player. Figma built Photoshop in the browser. Google Docs became a credible Office replacement.

Because Chrome was open-source, developers adopted it. Electron — the framework that powers Slack, VS Code, Discord — is just Chromium wrapped in a desktop shell.

Because Chrome auto-updated silently, web standards could evolve fast. CSS Grid. WebGL. Service Workers. WebAssembly. All shipped to billions of users overnight.

And because Chrome controlled the browser, Google controlled the platform. When they wanted to push progressive web apps, they added features to Chrome. When they wanted AMP (Accelerated Mobile Pages) to succeed, Chrome prioritized AMP URLs in mobile search.

The browser became the OS. And Google owned it.

The Legacy: The Platform Is the Prize

Today, Chrome commands 65% of global browser share. V8 powers Node.js, Deno, and most of the JavaScript ecosystem. Chromium — the open-source project — is the foundation for Edge, Brave, Opera, and dozens of others.

Microsoft, the company that once spent billions defending Internet Explorer, now builds their browser on Google's engine.

Larry Page's bet — that controlling the browser meant controlling the future of computing — was right.

The comic book that leaked on August 31, 2008 wasn't just a product launch. It was a declaration of war. And the 127-slide deck that followed on September 1st was the opening salvo in a battle that reshaped the internet.

Steve Ballmer came back from vacation to find Microsoft's 20-year monopoly in ruins.

And Larry Page never did another product launch again. He didn't need to.

The browser wars were over. Google had won.