Linked by Thom Holwerda on Thu 2nd Jul 2009 12:19 UTC
Whenever I use KDE, the part I dislike the most is the rendering engine used by Konqueror, called KHTML. KHTML just doesn't render pages as smooth and as well as Gecko and the KHTML fork WebKit, up to a point where I find Konqueror unusable as a web browser. However, work is underway to replace KHTML in Konqueror with WebKit, but according to KDE developer Adam Treat, this is a futile effort: Konqueror is too KHTML API specific.
Thread beginning with comment 371311
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2009-01-13
I have to agree with some comments that the KHTML devs are actually hurting KDE as a whole.
Complex web apps will never work in KHTML and giving people the illusion that that might change is bad. KHTML is a dead end.
Complex web apps will never work in KHTML and giving people the illusion that that might change is bad. KHTML is a dead end.
You can't blame KDE for trying to build a full desktop environment with a web browser and everything, but you can blame the distributions, they pick the defaults for users.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-01-04
This post started it all:
http://www.kdedevelopers.org/node/3995
I have to agree with some comments that the KHTML devs are actually hurting KDE as a whole.
Complex web apps will never work in KHTML and giving people the illusion that that might change is bad. KHTML is a dead end.