Recommended Posts

Apple claims Safari has quicker loading times than Opera, Firefox, and so on. They speak nonsense. The speed test, iBench 5.0, utilizes the JavaScript event OnLoad() firing to determine when the page is done loading. This is important to note because browsers have different definitions of when a page is "loaded." Opera will fetch the HTML, CSS, JS, and images before calling OnLoad(). Safari will call OnLoad() before it has fetched the CSS and images. This means the downloading and rendering times for the CSS and images are added to Opera's figures while they are not added to Safari's figures! Apple is being deceptive in presenting such fudged statistics as if they were valid.

Edited by megamanXplosion

For those that want you run WebKit you have to do the following:

Installing the Developer Tools

Getting the Code

Building WebKit

Running WebKit

Took about 3 hours in total to install/build everything, but boy is it worth it! I'm getting 93/100 on the Acid3 test, and blazing fast speeds, especially here on Neowin.

For those that want you run WebKit you have to do the following:

Installing the Developer Tools

Getting the Code

Building WebKit

Running WebKit

Took about 3 hours in total to install/build everything, but boy is it worth it! I'm getting 93/100 on the Acid3 test, and blazing fast speeds, especially here on Neowin.

Do you really have to do all that? All I did was extract the WebKit and replace the files in my Safari folder. I also get 93/100 on the Acid3 test. Just wondering.

Opera uses 40 mb of memory while Safari uses 64mb. Opera doesn't crash and its super stable. I think I will stick with Opera.

opera crashed on me today when I tried to take the acid3 test.

Anyway, I still use firefox as my main browser, I still consider opera as the fastest browser and now I totally think safari is a new contender. Maybe it wont be used my many people but at least we can say it's usable :p

How odd. My Safari on my XP is using only 7MB or RAM. Why many people says it use up to 50MB? Also when I test Acid3 page, I get 75/100.

I think it really depends what sites you are on if its demanding like Youtube and using flash it can really shoot the usage up.

Do you really have to do all that? All I did was extract the WebKit and replace the files in my Safari folder. I also get 93/100 on the Acid3 test. Just wondering.

Nah, You only really need to do that if you're making changes. Apple provide pre-built binaries for Windows and OS X (as you know)

Apple claims Safari has quicker loading times than Opera, Firefox, and so on. They speak nonsense. The speed test, iBench 5.0, utilizes the JavaScript event OnLoad() firing to determine when the page is done loading. This is important to note because browsers have different definitions of when a page is "loaded." Opera will fetch the HTML, CSS, JS, and images before calling OnLoad(). Safari will call OnLoad() before it has fetched the CSS and images. This means the downloading and rendering times for the CSS and images are added to Opera's figures while they are not added to Safari's figures! Apple is being deceptive in presenting such fudged statistics as if they were valid.

Actually no, its not apple being deceptive but yourself, cause if you care to read the newstory, Opera was not mentioned.

I thank You :woot:

Apple claims Safari has quicker loading times than Opera, Firefox, and so on. They speak nonsense. The speed test, iBench 5.0, utilizes the JavaScript event OnLoad() firing to determine when the page is done loading. This is important to note because browsers have different definitions of when a page is "loaded." Opera will fetch the HTML, CSS, JS, and images before calling OnLoad(). Safari will call OnLoad() before it has fetched the CSS and images. This means the downloading and rendering times for the CSS and images are added to Opera's figures while they are not added to Safari's figures! Apple is being deceptive in presenting such fudged statistics as if they were valid.

Actually no, its not apple being deceptive but yourself, cause if you care to read the newstory, Opera was not mentioned.

I wasn't referring to the news story. I was referring to the Safari website with the humongous barchart comparing Safari and Opera. (Another Neowin poster put up a screenshot of their bar-chart just a few posts before mine, which prompted my reply about the statistics being used.)

Apple's statistics were fudged because Safari calls the OnLoad event (reporting it's finished) before the images and stylesheets have been loaded and incorporated into the document (before it's actually finished). I have provided a barchart below that shows the difference between Safari and Other browsers in when they report that they're finished (notice the asterisk).

Safari

________*_______________________________________

|__html__|__css__|_____________images_____________|

Other

_______________________________________________*

|__html__|__css__|_____________images_____________|

So what are the nightly builds?

The WebKit engine is open source and gets updated continuously just like lots of other open source software gets nightly builds. Firefox for one. Safari uses the WebKit engine for its rendering of web pages. While the engine is open source and gets updated all the time. Apple builds the front end and is basically what Safari is. This gets updated only when Apple release a new version. Currently Safari 3.1 is based on a older build of the WebKit engine. Hence why some people are getting lower scores on the Acid 3 test than when using Safari 3.1 and the newer nightly builds of the WebKit engine.

So what are the nightly builds?

A nightly build is an unsupported version of a software, released daily, after the developers get batshit insane doing their stuff during the day. (They're released in end the working day, ergo, nightly.)

It's useful to track new features, test, check progresses and report errors to the developers.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.