The Browser: Google's Chrome

There is a browser that arrived this week, and the browser is the challenge: the Chrome that Google launched on Tuesday, the beta that runs on Windows, the software announced with a comic book by Scott McCloud, the code that takes on Microsoft's Internet Explorer. The launch happened on September 2, and the story spread through the week: the reviews, the downloads, the debate about what Google is building. The rationale is simple: Gmail, Docs, and Search need a faster browser, and Google is tired of waiting for someone else to build one. The browser is the September 2008 story, and the story is the lesson: the company that depends on the web must own the window to the web.

The Browser is the subject of this article: what Google announced, why the company built its own browser, what the launch means for Microsoft, for Firefox, and for the web.

1. The Announcement

The announcement is the comic, and the comic is the message: the forty page booklet that Scott McCloud drew for Google, the story that appeared on the company blog on Tuesday, the panels that explained the browser before the download existed. The announcement is the September 2 fact: the beta that launched for Windows, the version that Google called Chrome, the page that went live, the software that anyone could install that day. The announcement is the surprise: the company of search that shipped a browser, the project that was kept in secret, the morning that changed the browser wars.

The announcement is also the method, and the method is the choice: the comic book instead of the press release, the artist instead of the executive, the story instead of the spec sheet, the panels instead of the podium. The announcement is the Google way: the blog post that carried the booklet, the links that spread through the day, the coverage that followed this week, the downloads that mounted. The announcement is the contrast: the rivals who ship browsers with marketing events, the company that explained its software in pictures, the industry that had to read the panels to understand the design.

2. The Design

The design is the minimalism, and the minimalism is the interface: the tabs that sit on top of the window, the address bar that sits at the top, the buttons that are few, the chrome that is stripped away. The design is the omnibox: the single field that combines the search and the address bar, the box that guesses where the user wants to go, the feature that erases the line between typing and searching. The design is the statement: the browser that hides the machinery, the window that shows the page, the software that gets out of the way.

The design is also the speed, and the speed is the surface: the pages that render quickly, the tabs that open fast, the interface that never waits, that never slows. The design is the WebKit foundation: the engine that Apple uses for Safari, the rendering code that Chrome shares with the Mac browser, the base that was proven long before Google touched it. The design is the Google argument: the web applications that feel like desktop programs, the browser that feels like nothing at all, the experience that the company wanted for its own products, on its own terms, in its own browser.

3. The Engine

The engine is the speed, and the speed is the V8: the JavaScript engine that Google built for Chrome, the code that was designed for the modern web, the software that makes Gmail instant. The engine is the September 2 claim: the JavaScript that runs faster, the pages that respond sooner, the web applications that finally feel native, that finally feel fast, that finally feel real. The engine is the technical bet: the interpreter that was rebuilt from scratch, the compilation that happens at runtime, the performance that the old browsers could not deliver, the gap that the new engine closes.

The engine is also the message, and the message is the web: the JavaScript that powers the applications, the code that runs in every tab, the language that the whole industry bet on, the language that Google bet on too. The engine is the Google priority: the company that lives in the browser, that ships the web applications, that needs the speed more than anyone, more than any company on the web. The engine is the answer to the old model: the browser that was built for pages, the web that became programs, the JavaScript that became the platform itself.

4. The Security

The security is the sandbox, and the sandbox is the design: the tabs that run in their own cages, the web pages that cannot touch the system, the crashes that stay in one place, the failures that never spread. The security is the September 2 feature: the sandboxing that isolates each tab, the protection that works by separation, the model that treats every page as a suspect, every site as a risk. The security is the shift: the browser that assumes the web is dangerous, the software that plans for the attack, the defense that is built in from the start.

The security is also the privacy, and the privacy is the incognito: the mode that leaves no history, the windows that forget, the sessions that vanish when they close, the traces that disappear with them. The security is the updates: the browser that patches itself, the software that updates automatically, the fixes that arrive without the user asking, without the user knowing, without the user waiting. The security is the trust: the Google that handles the world's search, the company that asks for the browsing too, the promise that the data is safe, the question that the industry keeps asking.

5. The Open Source

The open source is the Chromium, and the Chromium is the release: the project that Google published on Tuesday, the code that anyone can read, the browser that is open at its core. The open source is the strategy: the engine that others can build on, the community that can contribute, the standards that can spread, the ideas that can be tested, the work that can be shared. The open source is the signal: the Google that shares the code, the company that invites the scrutiny, the browser that is judged in public, that lives in public, that grows in public.

The open source is also the reminder, and the reminder is the lineage: the Firefox that came from Netscape, the open web that Mozilla fought for, the challenger that Google helped fund and now faces. The open source is the continuity: the browser wars that were won by the open project, the code that proved the model, the history that Chrome now joins. The open source is the contrast: the Microsoft that keeps its code closed, the Google that opens its browser, the two strategies that meet in the same market, in the same week, in the same browser wars.

6. The Rationale

The rationale is the dependence, and the dependence is the web: the Gmail that Google runs, the Docs that Google ships, the Search that Google lives on, the applications that need a better browser, the apps that need a faster browser. The rationale is the September 2 logic: the company that could not wait for Microsoft, that could not wait for Firefox, that built the tool it needed. The rationale is the position: the search giant that was dependent on its rivals' software, the platform that was borrowed, the window that was rented, the window that had to be owned.

The rationale is also the future, and the future is the platform: the browser that is becoming the operating system of the web, the window that runs the applications, the layer that everyone must cross, the layer that everyone must trust. The rationale is the Google thesis: the web platform is the future, the browser is the gate, the company that controls the gate controls the path. The rationale is the timing: the launch that came this week, the moment when the web needed its own browser, the answer that Google wrote in code, the answer the web will now test.

7. The Reaction

The reaction is the war, and the war is the renewal: the headlines that said Google takes on Microsoft's Internet Explorer, the coverage that framed the launch as an attack, the browser wars that started again on Tuesday. The reaction is the threat: the Firefox that Google helped fund, the partner that became a rival, the open source browser that now faces a new competitor. The reaction is the analysis: the Google that is building an operating system in everything but name, the analysts who said it, the industry that nodded, the industry that understood, the industry that waits and watches.

The reaction is also the market, and the market is the share: the Internet Explorer that still dominates, the Firefox that rose as the open challenger, the field that Chrome enters from zero, the field that Chrome enters this week. The reaction is the question: the browser that Google launched in beta for Windows, the downloads that anyone can try, the reviews that pour in, the users who wonder what comes next. The reaction is the week: the reviews that ran, the downloads that grew, the debate that will not end by Monday, the debate that will last the year.

8. The Lesson

The lesson is the dependence, and the dependence is the warning: the company that depends on the web must control its own window, the browser that is the platform, the tool that no one else will build for you. The lesson is the Google example: the firm that saw the gap, that wrote the code, that shipped the browser, that took the risk. The lesson is the September 2008 story: the launch that happened on Tuesday, the beta that anyone can download, the future that is being written this week, the future the industry will watch in the months ahead.

The lesson is also the platform, and the platform is the web: the browser that is becoming the operating system, the applications that live online, the future that belongs to the open standards. The lesson is the engineering: the speed that was built, the security that was designed, the source that was shared, the craft that the project shows, the craft that the industry now judges. The browser is the September 2008 story, and the story is the lesson: the search company that built its own window, the web that became the platform, the browser that changed the game forever.

Tags

#technology #engineering