Apple’s upcoming Safari 3.1 will be 2.5 times faster

“When Apple chose the KHTML engine for its Safari Browser in 2003 over the more popular Gecko engine that powers Firefox, a lot of people were surprised,” Seth Weintraub reports for Computerworld. “Since then, Apple has really run with the KHTML engine, forking it off, renaming its development version “WebKit” and making it faster and leaner than Firefox on the Mac and both Firefox and Internet Explorer on the PC.”

“There is no other way to say it. Holy cow is this thing fast! I am currently testing Webkit build r30090 (more recent versions are now there) against standard Leopard Safari 3.04. This unoptimized WebKit build version is running circles around the standard Safari browser. It isn’t even close,” Weintraub reports.

“The newest Webkit is 2.5 times faster,” Weintraub reports.

“WebKit’s amazing, unoptimized speed means that Safari is going to get so much faster, to where it makes a significant difference in browser user experience. While Microsoft’s products are getting bulkier and slower, Apple’s products are getting leaner and faster,” Weintraub reports. “Safari is also the browser for the iPhone and iPod Touch, and these WebKit improvements will likely hit these devices as well. Probably about the time a 3G iPhone is released.”


  1. Apple is building products the same way we humans are built on cell structure. Each individual cell is fast and productive, but with in that cell are hundreds, thousands or even millions of cells that are each fast, effecient and powerful. Their code is getting leaner and faster because they understand that to make their dna as effecient as possible they must make each sub-set of code just as important as the primary.

    Truly, Apple is like water, fluid.

  2. well, what if you are on the east coast and working from home today?

    yawn… where is the coffee…

    I found 3.0 to be faster than 2 for me… but I think it was more to do with leopard than safari itself. perhaps they have just finished optimizing safari for leopard now…

    what seems amazing to me is how it “feels” like Apple has all its engineers working on one or two big projects at once, lots of attention placed on Safari now, Leopard before, iPhone before. Then, they get things working nice and SNAPPY and move on to the next item on the agenda. As opposed to other companies where they use a shotgun approach with everyone working on different projects trying to get them to work together somehow in the end… and you wind up with DLL errors. Like Microshit. Can I post that? ” width=”19″ height=”19″ alt=”grin” style=”border:0;” />

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.