Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I feel the difference between Safari 5.1.5 and Google Chrome 18.0 on Mac OS X 10.7.3 are very noticeable. The difference are most clear when it comes to reloading pages or XHR requests. Do Chrome somehow cached all these requests in a different way than Safari or have Google “hacked” Webkit to be speedier?
Thanks! =)
This is indeed very interesting, as the Webkit-Engine is build by Apple (!), not Google. To answer your question: Safari 5.1.5 uses Webkit 534.55.3, Chrome 18 uses 535.19. A minor difference, but still a plus for Chrome.
I my opinion the increase in “speed” is simply made by the way the browser renders a page: Safari seems to rebuild everything from scratch while Chrome (similar to Opera) build up the page even if it’s not fully loaded. Chrome has done a lot of these “feels faster” improvements (like loading browser GUI first, then loading libs. firefox does it other way round. which feels longer).
Update: An interesting article from Paul Irish of the Webkit Team on this topic. “Why Webkits aren’t the same everywhere”