Monday, March 02, 2009

Google Chrome v Internet Explorer: Pt. 4

Ever been surfing the web in Internet Explorer with multiple tabs or windows open when suddenly you’re face-to-face with the following error message? :

As if this interruption to your carefree browsing session weren’t enough, now every tab/window you were working in crashes before your eyes. Crafting a super long email? Better hope your email client backed it up for you. In the middle of an online purchase? Too bad, start over. The list goes on. Having a website malfunction is one thing, but why should that one website negatively impact your entire browser? It shouldn’t, and that’s why Google has employed the “sandbox” approach in Chrome.

In Internet Explorer, whether you’ve got 1 website open, or 11, they are all ultimately tied to the same central process. That means that if something goes wrong on one webpage, it can automatically affect all your other webpages. With sandboxes, Chrome gives each webpage its own process. That way, when something goes wrong, all you’ll have to deal with is the following error message.



Close that one tab and continue surfing. Because only that one process was affected, you won’t have to worry about losing any of your other sessions. Aren’t sandboxes great?

P.S. Try as I might, I was unable to make Google Chrome crash. I snapped the above photo based on the recommendations found on this page.