Linked by Thom Holwerda on Fri 29th Jan 2010 16:26 UTC
Permalink for comment 406827
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-07-13
KDE is committed to supporting KHTML through the 4.x release cycle, so dropping it is not an option. Besides, while I'll admit that KHTML may not be cutting edge, it is still very usable, a fact made more impressive considering that it is developed by a handful of people. It's worth remembering that the whole reason KHTML was chosen by Apple (versus Gecko) was the code base. It's no surprise that WebKit passed it by once Apple, and then others, poured resources into it.
It's still worth remembering where WebKit came from, though.
Having said that, you may want to give this a read, because clearly not all the KDE developers are pushing KTHML because it's "free"(?), or whatever.
http://aseigo.blogspot.com/2010/01/key-quest-webkit.html