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.

Thread beginning with comment 329471
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Skia
by Vanders on Sat 6th Sep 2008 21:20 UTC in reply to "Skia"
Vanders
Member since:
2005-07-06

The app should be using the system Cairo library, which will certainly be present on most modern Linux/Free desktops or installed automatically by your package manager.


Do you mean "app" as in Chrome or "app" as in WebKit? Cairo might be available on Linux or *BSD, but on other platforms frankly it's a huge pain in the backside to port and maintain, and I'd rather do without it.

Thankfully WebKit is nicely abstracted so it's not something I have to worry about: I won't have to use Cairo or Skia if I don't want too.

Reply Parent Bookmark Score: 2

RE[2]: Skia
by baadger on Sat 6th Sep 2008 21:36 in reply to "RE: Skia"
baadger Member since:
2006-08-29

I meant Chrome, because Webkit isn't an app.

Cairo has been 'ported' to Windows too, it has a solid Windows GDI back-end, and there are semi-official binaries for Windows on GNOME.org and at a few other sites.

And yes, Webkit is 'nicely abstracted' alright, except Cairo and Skia are already abstractions on other libraries such as various X libs/capabilities, GDI, SDL, OpenGL etc. Skia is being pulled into the WebKit tree, WebKit is being pulled into the Qt 4.4(?) tree as well into the GNOME desktop codebase for use in Epiphany's Webkit back-end. Both the GNOME and Qt/KDE platforms already have their own designated drawing libraries, Arthur and Cairo.

Just what is going on here? Why another drawing library?

It looks like Skia SGL was an acquisition: http://opengardensblog.futuretext.com/archives/2007/03/the_real_goo...

It seems to me that Skia SGL has little to do with 'competing' with Cairo on the desktop and more to with maybe getting Google's foot stuck further in the door with Opera on mobile devices.

Edited 2008-09-06 21:42 UTC

Reply Parent Bookmark Score: 3

RE[3]: Skia
by Vanders on Sun 7th Sep 2008 11:15 in reply to "RE[2]: Skia"
Vanders Member since:
2005-07-06

It seems to me that Skia SGL has little to do with 'competing' with Cairo on the desktop and more to with maybe getting Google's foot stuck further in the door with Opera on mobile devices.


Yes, and that makes a lot of sense from Googles perspective. Cairo is overkill on a mobile device, so Skia appears to be their answer to that.

Reply Parent Bookmark Score: 4

RE[3]: Skia
by TQH ! on Mon 8th Sep 2008 13:16 in reply to "RE[2]: Skia"
TQH ! Member since:
2006-03-16

Calling Cairo an abstraction to underlying graphics is not very accurate except maybe for X. It's more of a 'tail wagging the dog' kind of thing.

Reply Parent Bookmark Score: 1

RE[2]: Skia
by TQH ! on Mon 8th Sep 2008 13:12 in reply to "RE: Skia"
TQH ! Member since:
2006-03-16

Agreed. Cairo's code and project structure is among the worst I've seen so far.

Reply Parent Bookmark Score: 1