doron's blaahg

Well that started on aKademy where we discussed this on the first day. The question came up during a discussion I had with Matthias Ettrich and a few others. It is currently a pain to the user to need two installed browsers, one browser which works for this website and the other browser which works for the other website. Konqueror is fast and nicely integrated, but Mozilla renders more pages better.

Customers that do web application development heavily use DHTML and other special features that Konqueror doesn't handle very well and it is a lot of work to implement this. Although I like KHTML and the architecture quite a bit I am sad to say that probably the Gecko rendering engine will be the dominant one used in the enterprise arena, and as KDE developers we've got to make sure that we can integrate Gecko fairly well into KDE.

So Lars Knoll and Zack Rusin started working on this at aKademy and I was delighted when they put me aside and showed me what they have done in just three days. It is amazing! I think it is the right way to go! It is a bit sad for KHTML and I hope that despite this people will still maintain it as it is a nice lightweight browser. If it would be a purely technical decision, KHTML has the better architecture, but sometimes you need to go the shortest way to get to your target.

please forgive me if this is a stupid question or just blatantly incorrect (i know almost nothing about the K dev community), but it seems that most of the huge improvements to khtml that have been made thanks to apple and safari have yet to make it into konqueror. is this due to platform-specific issues, or are they just waiting to be patched in?

I don't know, but this comment sounds informed:

http://dot.kde.org/1097096753/1097113373/1097117951/

Any examples why "KHTML has the better architecture"? Or is this just a matter of taste?

It's fair to say that the KHTML code is a lot simpler, and Gecko suffers a lot more from premature optimization.

There's some feature that seem simpler to implement in KHTML than inside Mozilla.

See :
http://weblogs.mozillazine.org/hyatt/archives/2004_03.html#005130
and
https://bugzilla.mozilla.org/show_bug.cgi?id=9101

I think the link below is the reason why KDE is looking into Mozilla. I think Apple is treating them rather badly (notice the author of the post).
https://mail.kde.org/pipermail/khtml-devel/2004-July/001068.html

KHTML is better than Gecko, but Konqeuror sucks !

;o