This is a good hint, but Rob omitted the obligatory cautionary text. Nightly builds are development builds that have not been tested and quality assured for real world use. Many of the performance improvements that Rob mentions may introduce other bugs and cause your WebKit-based browsers to misbehave in various subtle or not-so-subtle ways. Furthermore, many other applications (e.g. Mail) use WebKit behind the scenes, which can cause mysterious bugs to appear in seemingly unrelated applications.

If you're going to use the nightly builds of a web browser, whether it's Safari, FireFox, or anything else, be aware that you are using software that has received only limited testing.

[ Reply to This | # ]

Just to clarify your comments for others...

The WebKit nightly build does not impact other applications that use WebKit. It's a wrapper around the nightly build of the webkit backend and, when you run WebKit.app, it just loads Safari with the updated webkit engine.

There's no replacement of your existing system libraries etc, so no impact on any other applications.

[ Reply to This | # ]

First, the above comment is the important part: The WebKit in nightlies is self-contained within the app package.

Second the only bugs should be displaying webpages, which is supposed to be better than regular Safari. In the past, I've never had problems with nightlies.

In fact I was just about to post 2 different methods of changing the WebKit homepage. However this is better in nearly every aspect.

[ Reply to This | # ]