I'm looking at iTunes 7 and I don't see any Aqua.. Is Aqua dead?

13»

Comments

  • Reply 41 of 45
    It's the rendering engine, of course, that's slower. As well as the startup times, and the JavaScript engine....



    Switching to Cocoa doesn't fix that.



    Camino's also in those benchmarks, and it's also ungodly slow.



    - Dr Turtle. PhD, bitches.
     0Likes 0Dislikes 0Informatives
  • Reply 42 of 45
    slewisslewis Posts: 2,081member
    Quote:
    Originally Posted by gregmightdothat View Post


    It's the rendering engine, of course, that's slower. As well as the startup times, and the JavaScript engine....



    Switching to Cocoa doesn't fix that.



    Camino's also in those benchmarks, and it's also ungodly slow.



    - Dr Turtle. PhD, bitches.



    The only thing slow about Firefox compared to Safari is the Startup times.

    Let me do a test and post the results, Google usually provides a good test seeing as how they provide the exact seconds.

    ...................|Test 1|Test 2|Test 3

    Safari.........|0.04s..|0.05s.|0.14s

    Camino......|0.07s..|0.09s.|0.10s

    Firefox.......|0.05s..|0.04s.|0.10s



    Test Keywords

    1: Elephant

    2: Apple

    3: a



    I should point out that a single letter by itself generally turns up more results

    Other Notes: The only thing I have open is the 3 Browsers and my Font Manager (which is always "Open") and Quicksilver. Camino also has 2 Windows Open, 1 with 4 Tabs because I'm using them.



    From my tests, Safari is as fast as Firefox, except for the last test. Safari topped Camino in the first 2, but not in the last one. Camino has the same Rendering Engine as Firefox, but it also had more windows and tabs open, with the other 2 browsers being 1 Window no tabs, because I didn't feel like closing the Window I was working in.



    The Conclusion:

    It doesn't really matter, especially since one of the reasons I don't use Safari is because it's not as Google Friendly, or Google isn't as Safari Friendly with everything. If you happen to use Safari, go ahead, but both Firefox and Camino still trump it.



    Firefox is slow at startup because of XULrunner, but once it's actually loaded it's very fast.



    Sebastian
     0Likes 0Dislikes 0Informatives
  • Reply 43 of 45
    Quote:
    Originally Posted by Slewis View Post


    The only thing slow about Firefox compared to Safari is the Startup times.

    Let me do a test and post the results, Google usually provides a good test seeing as how they provide the exact seconds.

    ...................|Test 1|Test 2|Test 3

    Safari.........|0.04s..|0.05s.|0.14s

    Camino......|0.07s..|0.09s.|0.10s

    Firefox.......|0.05s..|0.04s.|0.10s



    Test Keywords

    1: Elephant

    2: Apple

    3: a



    I should point out that a single letter by itself generally turns up more results

    Other Notes: The only thing I have open is the 3 Browsers and my Font Manager (which is always "Open") and Quicksilver. Camino also has 2 Windows Open, 1 with 4 Tabs because I'm using them.



    From my tests, Safari is as fast as Firefox, except for the last test. Safari topped Camino in the first 2, but not in the last one. Camino has the same Rendering Engine as Firefox, but it also had more windows and tabs open, with the other 2 browsers being 1 Window no tabs, because I didn't feel like closing the Window I was working in.



    The Conclusion:

    It doesn't really matter, especially since one of the reasons I don't use Safari is because it's not as Google Friendly, or Google isn't as Safari Friendly with everything. If you happen to use Safari, go ahead, but both Firefox and Camino still trump it.



    Firefox is slow at startup because of XULrunner, but once it's actually loaded it's very fast.



    Sebastian



    What?



    You didn't just post the time Google posts with your search results, did you?



    That's the time GOOGLE took to find your search. It has nothing to do with your browser rendering time whatsoever.
     0Likes 0Dislikes 0Informatives
  • Reply 44 of 45
    slewisslewis Posts: 2,081member
    Quote:
    Originally Posted by gregmightdothat View Post


    What?



    You didn't just post the time Google posts with your search results, did you?



    That's the time GOOGLE took to find your search. It has nothing to do with your browser rendering time whatsoever.



    I didn't think about that...



    Fine, do you have a better test?



    Either way the conclusion is the same.



    Sebastian
     0Likes 0Dislikes 0Informatives
  • Reply 45 of 45
    Quote:
    Originally Posted by Slewis View Post


    I didn't think about that...



    Fine, do you have a better test?



    Either way the conclusion is the same.



    Sebastian



    JavaScript test:

    http://www.24fun.com/downloadcenter/...s/benchjs.html



    CSS test:

    http://www.howtocreate.co.uk/csstest.html
     0Likes 0Dislikes 0Informatives
Sign In or Register to comment.