Chrome features are coming to WebKit

All I know is that Safari 4 should quarantine individual tabs into their own process. This, imo, is the best feature of chrome. Flash player plugin crashes are quarantined and base RAM usage is reduced.

Safari gobbles RAM like a fat chick at an open buffet for hedonists, which is fine if its aggressively caching, but when I clear the cache I only get back a fraction of that RAM. I'm not sure if this is due to fragmentation or just the aggressive cacheing system, which by the way is really only useful for people on dial-up modems or Edge/3G.

Browsing 15 sites, resetting, and then closing the Safari window shouldn't require Safari to still sit on top of 100MB+ of my RAM. Apple, please consider placing tabs' in their own process!

Google removed WebKit's HTML 5 database storage API from Chrome, but included their own non-standard database API from Google Gears: http://docforge.com/wiki/Google_Chrome

You just can't get away from this crap browser, can you? Even on a blog devoted to a platform that it doesn't run on.

Squirrelfish extreme is available in the latest nightly WebKit builds and gives a 20 - 30%! JavaScript speedup. In some cases it is (much) faster than V8, but Google's engine is (much) faster than Squirrelfish extreme on some other tests. Hope we soon see even more improvements.

My understanding of Squirrelfish Extreme is that while it shares the jit compilation approach of V8, it is not the same sort of implementation. Based on the published benchmarks that I've seen of it vs V8, Squirrelfish Extreme presents a roughly 40% speed increase.

Despite your revisions, this article is still incorrect. Neither V8 nor Skia are being added to the WebKit repository or included in any WebKit nightlies. Conditional support for using them as external components is starting to be added to the main WebKit tree, so that some time in the future the Chrome developers will be able to use this tree rather than their own fork. As far as I know, this work is nowhere close to being finished.

A lot of widget toolkits and graphics libraries are supported by WebKit, since it has been ported to many different systems, but none of them are "included" in WebKit. Nightlies are made for Mac OS and the Apple Windows ports, both of which use Apple's CoreGraphics library, not Skia.

The chance for a better alternative to the already good SquirrelFish is great, but I think the real benefit here for Safari users is that Google will not be ignored. This means that all those sites coded by lazy Windows-centric developers will no longer be able to ignore WebKit as it's been doing in the past. Even gov't sites won't let access their systems unless you are using IE or FF, even though it works just fine if you use Google's Cache to get to the login page. Sure, you can change your User Agent in Safari on the desktop, but on the iPhone/Touch you can't. It's like the nerdy, artistic kid just got the biggest, most popular kid in school to be his friend.

You seem to have a loose definition of "Mac" pertaining to running windows. If a user does employ either VMWare or Parallels, they are running windows on their intel based Apple computer, via the Mac operating system.

So it is only available to windows users, including those with Apple computers with intel processors.

"lthough the WebKit project has its own new JavaScript engine, SquirrelFish, Mobile Safari and the WebKit nightlies are including V8 along with the Skia graphics library."

I say hogwash! Just check out the code yourself.

http://trac.webkit.org/browser/trunk/WebCore/config.h#L150

"Currently Chromium is the only platform which uses V8 by default" Hmmm...

V8 is not in the current WebKit nightlies. Please correct the post.