Why Google Built Chrome to Break Apart

Why Google Built Chrome to Break Apart When one page fails, what happens to the rest of your work? Early Chrome treated the browser as a place for running applications, with consequences for crashes, responsiveness, memory and security. This film follows the choices behind that separation: connected pages that had to stay together, experiments in early Chromium, and the costs of keeping other work available. The measurements discussed are from a 2009 study of Chromium 0.3.154 on a dual-core Pentium D running Windows XP SP3. They are not current Chrome benchmarks. Sources Google, “A fresh take on the browser” (September 1, 2008): https://googleblog.blogspot.com/2008/... Google, “Google Chrome, now live” (September 2, 2008): https://googleblog.blogspot.com/2008/... Charles Reis and Steven D. Gribble, “Isolating Web Programs in Modern Browser Architectures,” EuroSys 2009: https://www.charlesreis.com/research/... Google, Chrome for Mac, Linux and extensions betas (December 8, 2009): https://googleblog.blogspot.com/2009/... Historical images and credits Chrome displaying Wikipedia: Navy Blue, original September 2, 2008 revision, Wikimedia Commons. Cropped/scaled for commentary. Software screenshot BSD terms; Wikimedia text CC BY-SA 4.0 / GFDL; trademarks remain their owners’ property. https://commons.wikimedia.org/wiki/Fi... https://creativecommons.org/licenses/... Chrome promotional screenshots: Google, reproduced in Philipp Lenssen’s September 2, 2008 Google Blogoscoped report. Used in limited excerpts to discuss the original interface. https://blogoscoped.com/archive/2008-... Linux GTK-theme and extensions images: Google, December 2009 announcement above. Chrome identity reference: Google’s March 21, 2011 old/new icon comparison. The thumbnail is an original illustrative material reinterpretation, not archival hardware. https://chrome.googleblog.com/2011/03... Paper title and short excerpts: Reis and Gribble / ACM, EuroSys 2009. Limited excerpts accompany criticism and explanation; rights remain with their owners. AI disclosure Narration uses a synthetic voice. Original AI-assisted illustrations depict hypothetical people, situations and physical analogies; they are not photographs of real employees or historical events. Process demonstrations are authored explanatory diagrams, not captured historical software or tests performed by this channel. Genuine historical screenshots and source excerpts are identified separately. Terms of Progress explores the choices behind familiar technology.