Linked by Thom Holwerda on Sun 15th Aug 2010 18:22 UTC, submitted by Debjit
KDE "We always knew that WebKit is going to make Konqueror fast; but how much faster? Today we test that by putting Konqueror with KHTML through the SunSpider JavaScript Test and the then do the same with WebKit. To get an idea of how fast they are compared to other browsers, we also decided to put Firefox 4.0 Beta 2 through the tests."
Thread beginning with comment 436898
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Why only now?!
by ssokolow on Sun 15th Aug 2010 19:40 UTC in reply to "Why only now?!"
Member since:

As I understand it, QtWebKit didn't expose APIs required for feature parity when KDE 4.0 was released and their API stability policy requires that all APIs present in 4.0 remain throughout the release cycle, so that might have been a drag or disincentive on KWebKit development.

(That API stability policy and having been burned by an earlier GStreamer release is actually what lead to Phonon... apparently at least one GStreamer dev showed quite a lack of maturity at that development.)

Of course, API stability and functional stability are two different things. As much as I like the idea of KDE, I switched to LXDE after waiting through 4.4, still having too many bugs, and discovering that one guy in a basement can easily have a more thought out release testing plan than the KDE guys. (It also doesn't help that they see no problem with the "chuck it all out and start over" pattern that appears at every major version increment with regards to features and stability)

Edited 2010-08-15 19:41 UTC

Reply Parent Score: 4

v RE[2]: Why only now?!
by tyrione on Tue 17th Aug 2010 03:46 in reply to "RE: Why only now?!"
RE[3]: Why only now?!
by smitty on Tue 17th Aug 2010 06:42 in reply to "RE[2]: Why only now?!"
smitty Member since:

I'm not sure i understand your point.

The KHTML devs split in half a while ago - half continued development on it, while insisting that Apple and Webkit were evil and not integrated into KDE well enough to replace khtml.

The other half went to work for Trolltech integrating Webkit into Qt. Eventually, those same people, along with a few others from the community that were trying to use Webkit in their projects, finished the integration work with Webkit/KDE.

Reply Parent Score: 3