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.
Permalink for comment 371335
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2007-12-08
Well, that sucks if it's accurate. The browser is arguably the single most important program on a desktop today, and it bugs me that it's also the only non-kde app I use on my desktop. I keep hoping the webkit kpart will improve, because it seems 'so' close to being usable. And khtml/kjs....sorry, they're just not an option for me. Slow, incompatible, and not seeming like they're going to be changing that any time soon.
Like someone above, I'm using chromium on linux right now because that pre-alpha is actually better at rendering pages than konq is. And that's a pretty sad statement.
I don't want to seem like I'm not grateful for all the hard work that's gone into khtml. It got us to webkit in the first place. But it's clinging to a dead horse at this point.
Is there any work going on right now in making a kde (not just qt) based browser using webkit?