You likely also know that Safari is implemented using WebKit, an open source framework for embedded HTML clients. It's at that point that the relationship between Safari and WebKit becomes hazy. The common belief is that Safari is effectively a front-end wrapper for WebKit.

[ Safari is ahead of the curve in speed, standards, and good looks, but not in security -- find out why in the . ]

I'll set that record straight. The default browser on all of my Macs is named WebKit.app. There is another program in the Applications folder named Safari.app. When I launch WebKit.app, the menu bar shows the name "Safari." WebKit is Safari, plus everything the independent WebKit project folds into its nightly builds. Those builds are released as source and as Windows and OS X executables that users are not warned away from, but encouraged to use.

Safari is WebKit frozen at a stable release, validated, supported (except for betas), and documented by Apple. That's essential added value given that WebKit joins Core Data, Core Animation, and other Apple frameworks that provide developers with one way, a right way, to incorporate any application feature. The safe, supported WebKit and its vastly accelerated JavaScript interpreter will move developers to shift more applications to the Web. Steve Jobs spoke of this at the iPhone announcement. He just spoke too soon.

Racing JavaScript