Google Chrome — A Fresh Browser Engine

Google Chrome arrived yesterday as a Windows beta with a comic explaining multi-process tabs and a reputation for speed. Another browser is the last thing some people wanted. For web developers and security folks, it is a big signal: the rendering engine wars are back.

Mac and Linux versions do not exist yet. This is a Windows-only beta — but the design choices are worth studying regardless of platform.

What Is Different

• Separate processes per tab — one crash does not take down everything
• Sandboxing ambitions — harder for web content to touch the system
• V8 JavaScript engine — fast enough to change how web apps feel in the browser
• Minimal UI — the address bar doubles as search, fitting Google’s habits
• Incognito mode — private browsing without digging through menus
• Silent auto-update — patches ship without a user-facing version bump

Chrome uses WebKit for rendering — the same engine family as Safari — with Google’s own V8 replacing JavaScriptCore for script execution.

The Comic and the EULA Scare

Google published a Scott McCloud comic explaining the architecture before launch. That was unusual and effective — engineers could read the multi-process model before downloading the installer.

The first-day EULA controversy (language suggesting broad rights to content submitted through Chrome) was walked back quickly. It reminded people to read license terms even on beta software from trusted brands.

Should You Switch Immediately?

Not required. Many keep Firefox 3 for extensions and IE7 for captive intranet sites. Chrome is still worth installing because:

• It exposes layout bugs in your CSS that IE7 masks
• It accelerates JavaScript-heavy experiments — maps, mail, spreadsheets in the browser
• It pushes competitors to improve performance
• It previews web apps that feel closer to desktop software

Extension support is not here yet. Google has said it is coming. For now, Chrome is a second opinion, not a full replacement.

Security Notes Early On

New browsers bring new bugs:

• Update channels matter from day one — the beta will move fast
• Plugins (Flash, etc.) run outside the sandbox — same weak spots as other browsers
• Phishing still relies on user judgment, not only the browser
• Privacy questions around Google’s combination of search, mail, and now browsing history

Report crashes through the built-in feedback tool. Beta means beta.

For Web Developers

Test your sites in Chrome alongside IE7 and Firefox 3. Pay attention to:

• CSS floats and clears — WebKit handles them differently from IE
• JavaScript that assumes ActiveXObject — it will not run here
• Fixed-position elements and overflow — common gotchas in WebKit

Google’s own apps — Gmail, Google Docs, Maps — are the reference implementation for what Chrome is optimized to run.

Install It as a Test Browser

Chrome in 2008 is not just “Google’s browser.” It is a bet that mail, maps, documents, and heavier JavaScript apps belong inside the tab.

You do not need to move your daily browsing there yet. Install it as a test browser, run your sites through it, and watch how quickly performance expectations change.