Dear PlanetKDE/Lazyweb,
I am curious about the future of KHTML in the face of WebKit. Three questions come to mind:
- Why does KDE use KHTML when WebKit is faster, more compatible, etc?
- Why does Konqueror use KHTML as default instead of WebKit?
- Will KHTML be moved out of the main tree?
As far as I can see, it is commonly accepted fact that WebKit is a faster and more compatible engine than KHTML. WebKit was ported to Qt in 4.4, and Qt 4.5 provides some critical enhancements. From these two points, the three questions above naturally follow. If the situation for KHTML was completely hopeless, then it never would have made KDE 4.0 or the present API would be converted into a wrapper for QtWebKit. But this is not the case, so presumably the KHTML team has high hopes for the project. I wonder what the team’s response is to these questions. Undoubtedly they have thought a lot about KHTML vs WebKit and find WebKit a worthwhile project. What’s the deal?