Google Enters the Web Browser War
If you haven’t seen the buzz in the blogosphere yet, Google is releasing their own web-browser, dubbed Chrome, tomorrow. I just perused the info-comic (made by Scott McCloud of all people) explaining the ideas and architecture behind Chrome, and I must say that I’m curious.
Here is what stands out to me:
- Multi-process *and* Multi-threaded – Each browser tab will be its own separate process with its own thread pool. If a website causes a crash, the whole browser won’t go down–only that one tab. There will also be a built-in task manager that will enable you to kill processes and threads and also identify exactly what is causing the crashes. This will require more memory up front, but could potentially save memory in the long run.
- Process compartmentalization – Google reinforced process boundaries to an even higher degree to prevent malware attack and bad plugins from hosing the entire browser. The “sandbox” (as they call it) is completely user driven.
- Using WebKit – The Webkit rendering engine is fast, light-weight and used in both conventional laptops/desktops and mobile devices. Potential iPhone app anyone?
- Omnibar – This will be Chrome’s equivalent to Firefox’s “Awesome” bar, or what we traditionally refer to as the location bar.
- Open Source – Google’s entry into the browser war can only help the internet as a whole. The entire Chrome project will be open sourced so I’m sure we’ll start to see some of these features absorbed into Firefox, Safari, IE (maybe), etc.
- Stability – Google has an index of, I daresay, trillions of webpages. Apparently they are subjecting test builds of Chrome to millions of websites each day and are approaching asymptotically that “100% compatibility” mark.
Google Chrome is available for download now for Windows users.
Sorry, the comment form is closed at this time.