Between the time you click a link and a web page finishes loading on your iPhone, there are many factors that ultimately decide just how fast that process will be, including connection speed (2.5 G EDGE/3G HSDPA/WiFi) CPU speed, and rendering engine. Like desktop Safari, Mobile Safari uses Apple's open source WebKit rendering engine, and it seems like for 2.0, WebKit has gotten its turbo on, especially in handling Javascript. Says Daring Fireball:
For all the hubbub regarding the new App Store, most “iPhone software” runs in the web browser. But improvements in WebKit performance often help native iPhone app performance, too — a slew of my favorite native iPhone apps have built-in WebKit browsers (e.g., NetNewsWire, Twitterrific, Instapaper, and Cocktails). When WebKit performance improves, any app that uses WebKit improves, and WebKit improved a lot between iPhone 1.1.4 and 2.0.0
The original iPhone on 1.0 was already fast compared to some 3G phones because of the speed of its CPU and the optimization of its WebKit engine. Now it's getting silly fast. And I don't think we've even gotten the extra nitro from the new Safari 4 and SquirelFish tech yet either?
Check out Daring Fireball for the graphs and stats...
