<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3395" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=046445012-04092008>Well, I read the whole comic book about all the great
features and I focused on the process separation and memory mgmt and tried to
follow the stuff about the new VM. It all sounds good, sounds like
the way I'd do a browser if I knew how to do such a thing, but I have to say
that I thought that Firefox was working on doing these things in v. 2 and
3. You know, work to crash less and fix memory leaks.
Anyway, this explains why Firefox still crashes and takes everything with
it. Google Chrome should not let one tab w/ a problem bring the
whole browser crashing down.</SPAN></FONT></DIV>
<DIV> </DIV>
<P align=left><FONT size=2>Brian Kelsay</FONT></P>
<P align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Nathan Cerny<BR><B>Sent:</B> Wednesday,
September 03, 2008 11:43 PM<BR></FONT><BR></P>
<DIV></DIV>
<DIV dir=ltr>While that was interesting, most of the points were moot.
Yes, almost everything in chrome is something someone else has already came up
with. But chrome took all the good points from all these other browsers
and created a browser that implements them all well.<BR><BR>And this site seems
to imply that chrome should be running far more resource-dependant than the
other browsers out there - I have been running it since it's release yesterday,
and I am very impressed. It outperforms IE7 in all aspects...and IE7
outperforms firefox 3 in all aspects (I was shocked too when I realized
it). Of course, this is all on my computer at work, because I run only
linux at home ;)<BR><BR>Overall, chrome is an amazing browser with a lot of very
well-implemented ideas. The ideas themselves are not revolutionary, but
the implementation is...just like what gmail did to email, chrome is doing to
browsers.<BR><BR>My 2 cents :)<BR><BR><BR><BR><BR>
<DIV class=gmail_quote>On Wed, Sep 3, 2008 at 8:20 PM, Luke -Jr <SPAN
dir=ltr><<A href="mailto:luke@dashjr.org">luke@dashjr.org</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><A
href="http://www.osnews.com/story/20244/Google_Chrome_Considered_Harmful/page1/"
target=_blank>http://www.osnews.com/story/20244/Google_Chrome_Considered_Harmful/page1/</A><BR><BR>Also,
as far as the Linux version goes... they haven't even decided what<BR>toolkit
they'll be using. The current code is all
"windows.h"</BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>