IE 8 puts the tabs in separate processes.
Where Chrome's architecture excels is that JavaScript and plugins are
also in separate processes, so a failed plugin or off-the-rails script
won't bring down the main tab process.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Jeffrey Day
Sent: Monday, September 22, 2008 7:39 AM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] Google Chrome
Hi,
I like Chrome. I think simplifying the browser was a great idea, it
doesn't need to be as complicated as M$ makes it.
I think I like Firebug's DOM inspector more than Chrome's, and
definitely more than IE Developer Toolbar.
I thought I read somewhere that in IE8, the tabs were in separate
processes as well... so I don't think Chrome is the only one to do that.
-Jeff
On 9/20/2008 at 4:29 PM, in message
<000301c91b5f$878b34a0$96a19de0$@oprey@xmli5.com>, "Maurice O'Prey"
<maurice.oprey@xxxxxxxxx> wrote:
Hi All
I just wondered what peoples first impressions of Google Chrome Beta
are?
Checkout the element inspector (right click on any element in a web
page).
http://www.google.com/chrome
This could be a very interesting one... (for everyone)
Kind Regards
Maurice O'Prey
As an Amazon Associate we earn from qualifying purchases.