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 329587
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: And Mozilla?
by 0brad0 on Mon 8th Sep 2008 01:06 UTC in reply to "RE: And Mozilla?"
Member since:

That's funny. Essentially the only project that uses Gekco is Firefox and everyone under the sun is using WebKit. That speaks volumes about how bad Gecko is from a developers perspective. Also the fact that a very large number of developers for Apple, Google and other companies/projects are ex-Firefox developers and they all think WebKit is better in every aspect. WebKit was also the first HTML rendering engine to have full support for ACID2/ACID3 and the best draft HTML5 support. Firefox/Gecko is a complete disaster. It is just another example of people using the "most popular" piece of software but it does nt mean it is good at all.

Reply Parent Score: 4

RE[3]: And Mozilla?
by FishB8 on Mon 8th Sep 2008 05:16 in reply to "RE[2]: And Mozilla?"
FishB8 Member since:

That's funny. Essentially the only project that uses Gekco is Firefox and everyone under the sun is using WebKit.

Think again. There are quite a few projects that employ Gecko. Try looking and see how many programs use xulrunner. (That's basically the standalone Gecko library)

Remember, Gecko is much more than just an HTML rendering engine. It's a development platform. Some apps that employ it may have very little in common with a web browser. Take Miro for instance, or SongBird.

Characterizing Gecko as a "disaster" sounds too much like a WebKit fanatic with little insight. WebKit is very good, and improving, and perfect for handheld architectures. But don't write off Gecko. It has it's own advantages in certain areas over Webkit as well. Especially in dealing with XML based technologies for web applications.

Reply Parent Score: 3

RE[4]: And Mozilla?
by TQH ! on Mon 8th Sep 2008 13:37 in reply to "RE[3]: And Mozilla?"
TQH ! Member since:

From a development perspective he has a point. There is very much programming going on in the preprocessor and platform specific code is found everywhere even in the javascript-code. Unfortunatly the people working on development only seem to add to this mess rather than trying to clean it up. The mozilla-code is in need of a huge refactoring to be attractive to anyone.

For instance this header (71k) really should be divided to platform specific ones instead of preprocessor programming:

Reply Parent Score: 2