Re: First looks - Google Chrome: how does it stack up to the competition?
Quote:
Originally Posted by
directhex
Yeah, nothing kicks a Webkit browser's ass like... a Webkit browser
Wait, what?
Given that both Google and Apple have shouted about the speed of their JavaScript engine I think a comparison of the two would be useful.
Re: First looks - Google Chrome: how does it stack up to the competition?
Comparing web site load times doesn't really tell you anything useful - at least from an end user perspective. What I'd like to know is how much of a performance hit do you get as you increase the number of open tabs?
Quote from Jon von Tetzchner, Opera's CEO:
Quote:
Because Chrome is designed for running web apps, he says, "the focus is on keeping different processes for different windows - that's a very heavy duty thing to do. It's an OS approach rather than a browser approach." And something not considered worth following.
From the original article on the Register.
Anywy, don't trust Google so wont be installing their browser anytime soon.
Re: First looks - Google Chrome: how does it stack up to the competition?
Quote:
Originally Posted by
Vroomparrot
Comparing web site load times doesn't really tell you anything useful
it tells you how quick pages load in different browsers... which is useful...
Re: First looks - Google Chrome: how does it stack up to the competition?
Quote:
Originally Posted by
Vroomparrot
Anywy, don't trust Google so wont be installing their browser anytime soon.
audit the source. base comments in reality.
Re: First looks - Google Chrome: how does it stack up to the competition?
Quote:
Originally Posted by
Vroomparrot
Comparing web site load times doesn't really tell you anything useful - at least from an end user perspective. What I'd like to know is how much of a performance hit do you get as you increase the number of open tabs?
depends how you define "performance hit"
there will, unquestionably, be worse per-tab memory scalability with the chrome design. however, you can monitor the specifics if you like (press shift-esc or visit about:memory), and splitting things into processes essentially means a web page can't crash the browser (a process dies, just carry on as normal)
you also won't ever get the whole-browser slowdown you get when doing "heavy" things in one tab in other browsers - especially on a multivore CPU. this one's frustrating with FF, so eliminating it in chrome is great
Re: First looks - Google Chrome: how does it stack up to the competition?
Quote:
Originally Posted by
cobhc
No need to be sarcastic about it.
That's his "thing"
Re: First looks - Google Chrome: how does it stack up to the competition?
Re: First looks - Google Chrome: how does it stack up to the competition?
How does it stack up? Answer - not well enough! - yet
Re: First looks - Google Chrome: how does it stack up to the competition?
Apparently this beta release is using an older version of Webkit (v525.13) so some of the recent Webkit development improvements are not present. (According to Neowin)
I don't know how major those improvements are - but something to bear in mind perhaps.
=TcQi=
Re: First looks - Google Chrome: how does it stack up to the competition?
Also quoting Arstechnica:
"as Ina Fried of News.com points out, Chrome's "Omnibar" can also access all keystrokes a user types, and Google will store some of this information along with IP addresses."
Hmmm... Nah, you're alright thanks. I'll stick with FF3
