Thread: WebKit engine for default browser
View Single Post
BrentDC's Avatar
BrentDC is offline BrentDC
2009-01-17 , 01:04
Posts: 903 | Thanked: 632 times | Joined on Apr 2008
#306
Originally Posted by Bundyo View Post
I won't call running javascript cheating - doubt that WebKit counts it too. Its another thing that js in Webkit is much faster than in the more than a year old Gecko engine in MicroB...
Isn't that the point? Speed of a browser basically involves three things:

1) Downloading the raw data
2) Rendering the page (interpreting the HTML, CSS, etc.)
3) Executing the Javascipt.

Of course, there are probably others, but those are the big ones...

When we crown a champion of the "faster web browser" would it not be unfair to exclude one of the major things that determine "speed"? Maybe MicroB isn't cheating by executing javascipt, but we are cheating webkit by not including this (very important) determinate of speed into the equation.

I tested Webkit on Dealnews.com; CPU usage dropped 1-2 seconds after webkit indicated the page was done loading.