Linked by Thom Holwerda on Sat 6th Sep 2008 19:56 UTC, submitted by KAMiKAZOW
Internet & Networking

The WebKit team is currently busy, integrating the patches made for Google Chrome into the main WebKit repository. This includes the new V8 JavaScript engine and the Skia graphics library. Most integration work is done by Google employee and WebKit reviewer Eric Seidel. V8 is a fast, BSD licensed JavaScript engine that runs on 32bit x86 and ARM CPUs. Due that platform restriction, V8 probably won't replace WebKit's new SquirrelFish engine anytime soon as default, because SquirrelFish has broader CPU architecture support. Epiphany developer and WebKit reviewer Alp Toker gives an overview about Skia. Unlike V8, Skia is licensed under the Apache License 2.0. Some of Skia's main features are optional OpenGL-based acceleration, thread-safety, 10,000 less lines of code compared to Cairo, and high portability.

Permalink for comment 329635
To read all comments associated with this story, please click here.
RE[4]: And Mozilla?
by Vanders on Mon 8th Sep 2008 14:08 UTC in reply to "RE[3]: And Mozilla?"
Member since:

Firstly I said that Gecko was far more mature than Webkit- I did not say that Webkit is immature. Gecko is the result of almost 15 years of fine tuning for millions of web pages. Webkit is very young in contrast-being perhaps 3-4 years old at the most.

Where do you get those dates from? KHTML/WebKit is at least as old as Gecko.

Although I am no expert in either the Webkit or Chromes code base it seems obvious to me from the comic published by Google that they must have made rather significant changes to the Webkit code. According to that comic when they first started to use Webkit they were only getting 23% compatibility-ie. only 23% of the pages rendered like they normally would with Webkit. Now they claim to have 99% compatibility. I of course cannot explain to you exactly what changes needed to be made- but it seems obvious that both V8 and Webkit needed to be modified to work correctly together to get correct rendering.

For WebKit to render correctly the platform implementation must be complete, as it necessarily implements a lot of the low-level rendering code. Things like rounded corners, gradient fills etc. are all platform-specific. If you're starting with a new port you'll find that page rendering is not comparable to existing ports. It is likely that all Google mean by their comic is that their WebKit/Skia combination started out as a basic skeleton and was developed until it matched 99% of the functionality in the other platforms.

Replacing JavaScriptCore/SquirelFish with V8 didn't require any major changes to the rendering engine either, as the two are nice and cleanly defined within the source tree.

Reply Parent Score: 5