Chrome didn’t fix the web—it weaponised speed and isolation, then abandoned standards compliance when it suited Google’s control.
Chrome is a fast, isolated, Windows-first browser built for developer velocity—not web interoperability. Its 2008 launch reset performance expectations but entrenched vendor control over core web infrastructure. Its technical strengths are real and measurable. Its compromises are deliberate and documented.
Chrome launched as a Windows-only beta on September 2, 2008, with 43-language support.
2:37
Speed Advantage
In 2008, Chrome beat every major browser in JavaScript and computational benchmarks.
3:40
Process Isolation
Each tab and plugin runs in a separate, sandboxed process—enforcing memory and resource isolation.
5:04
Standards Compliance Window
Chrome passed Acid1 and Acid2 at launch; passed Acid3 from v4.0 until April 2017.
6:19
Engine and Assembly
It began with WebKit, forked WebCore into Blink in 2013, and relied on 25 third-party and Google libraries.
7:26
Security Model
Its sandboxing model mirrors IE9’s Protected Mode—but applies it by default to every tab.
Worth your time?
Yes. Study the whole thing.
4/ 5
What works
process-per-tab isolation
JavaScript benchmark dominance in 2008
Acid1/Acid2 compliance at launch
Acid3 compliance from v4.0 to April 2017
What does not
Acid3 compliance after April 2017
NPAPI plugin support after v45
cross-platform launch (it was Windows-only at release)
Study it if
Windows XP+ developers in 2008
teams needing crash-isolated tabs
organisations prioritising JavaScript speed over standards fidelity
Skip it if
standards-compliance auditors post-2017
enterprise environments relying on legacy NPAPI plugins
non-Windows users before 2009
The written brief1 min read
What it is and the problem it solves
Chrome is a Windows-only beta browser launched on September 2, 2008. It solves slow JavaScript execution and insecure tab sharing in existing browsers. It targets developers and power users who prioritise speed and crash containment over standards completeness or cross-platform parity.
How it works
Chrome uses a multi-process architecture. Each site instance and plugin runs in its own process. It applies the principle of least privilege to sandbox tabs. It isolates memory access between processes. It was assembled from 25 code libraries including Netscape Portable Runtime, Network Security Services, Skia, and SQLite.
What works
It passed Acid1 and Acid2 at launch. Version 4.0 passed Acid3 until April 2017. In 2008 benchmarks, it outperformed Safari (Windows), Firefox 3.0, IE7, IE8, and Opera on SunSpider and Google’s ray-tracing and constraint-solving tests.
What does not
Chrome no longer passes Acid3 as of April 2017. It dropped NPAPI support as of version 45. Its initial WebKit reliance meant it inherited WebKit’s constraints until the 2013 Blink fork.
What it changes
It redefined browser security expectations by normalising per-tab process isolation. It accelerated adoption of V8-based JavaScript execution. It shifted rendering engine control from open consensus (WebKit) to vendor-led evolution (Blink).
Is it worth your time
Yes—if you need speed and isolation on Windows XP or newer in 2008. No—if you require Acid3 compliance after April 2017 or depend on NPAPI plugins after v45. Its value is situational, not universal.