QtWebKit vs. KHTML - again...
Posted by George Wright Tue, 30 Jun 2009 23:00:00 GMT
After reading Will’s latest post, I feel I have to chip in.
I am a long time user and huge fan of KHTML. I still use KDE 3, and my day-to-day browser is still Konqueror from KDE 3, using an old version of KHTML. For 99% of websites that I visit, this is sufficient. Notable exceptions are YouTube and Facebook, both of which are very AJAX-heavy, and I keep a separate Firefox (well, Iceweasel) window open for them on a permanent basis.
Why do I keep both browser windows open? Well, for general Googling, random surfing, wikipedia, etc, I love the sheer speed of Konqueror, and its configurable web shortcuts (such as gg:, wp: etc) are insanely useful. Scrolling is blisteringly fast on just about any webpage and everything happens instantly. This is one of the major reasons why I don’t use KDE 4 yet - Konqueror 4 just doesn’t seem that fast anymore. I realise this is all very subjective, but things don’t quite feel so fast anymore.
However, this is a very suboptimal solution. As Will says, KDE needs a good web browser that can integrate with the rest of the desktop, and people shouldn’t need to resort to alternatives like Gecko. Personally, I hate Gecko. It’s got a massive memory footprint and it’s not as fast as I would like.
I’m not going to be flavour of the month for suggesting this (am I ever?), but I’d say the best thing to do at this point is for the developers to forget about KHTML, and start working upstream on WebKit, as well as work on integrating WebKit with Konqueror. Yes, there are probably some very good reasons as to why this is not great for KDE, but are they good enough to justify hindering the entire project’s success? WebKit Qt isn’t perfect yet (it can’t handle Facebook Chat particularly well, for example), but it’s still a lot better than KHTML at the moment. There’s a KPart being developed to allow WebKit to render inside Konqueror, and all it needs is a bit of polish before we can maybe start using it full time. In fact, now that I have time and I’m going to be working on WebKit as part of my job, I’ll look seriously into getting into core Konqueror development.
Call me crazy, but back in ‘02 Konqueror was the browser to have - it was fast, it worked on every website (back then), it was slick and it was KDE. I’d like to be able to go back to that, but fast forwarded 7 years!
