This forum has been archived. All content is frozen. Please use KDE Discuss instead.

[Konqueror]Develop the KHTML again

-1

Votes
0
1
Tags: None
(comma "," separated)
bobwong
Registered Member
Posts
3
Karma
0

[Konqueror]Develop the KHTML again

Sat Feb 29, 2020 8:58 am
You stopped developing the Konqueror in 2016, and now you are developing falkon which is a browser based on chromium. As a free-software project, You should support your own core of the browser. The Konqueror uses KHTML, which is developed by yourselves 20 years ago. It may be the only core developed by the community now. And the WebKit is based on the KHTML. So maybe it is a good idea to develop a browser(maybe not Konqueror) to support the KHTML.
airdrik
Registered Member
Posts
1854
Karma
5
OS
Sounds like a lot of wasted (duplicate) effort, if you ask me; unless anyone has any reason to believe they can make something better than the existing rendering engines - more standards-compliant, more performant, better able to keep up with changes to the standard, etc.
The problem is that we're talking about whole generations of browser rendering technology. As great as KHTML was in its day, it's become quite the dinosaur in comparison to modern webkit, blink and gecko rendering engines. A large part of the problem is modern javascript and css requirements. Vast changes and enhancements have been added to the standards in the last 10 years or so that haven't been touched in KHTML. Not to mention the ongoing effort to keep up as the standards continue to evolve. That alone was a formidable enough challenge that even QT decided the best way to provide relatively up-to-date html rendering support was to basically bundle (a fork of) chromium's rendering engine as the QtWebEngine component (which, by the way, is available as the current default view mode in konqueror for web pages).

In short, I think that it would be a monumental effort to pull KHTML into compliance with modern standards. An effort hardly worthwhile when there are alternatives readily available.
Let KHTML be remembered as as the ancestor to the rendering engines used by most browsers today (all except firefox if I am not mistaken).


airdrik, proud to be a member of KDE forums since 2008-Dec.
User avatar
raphaelra
Registered Member
Posts
209
Karma
0
OS
bobwong wrote:And the WebKit is based on the KHTML. So maybe it is a good idea to develop a browser(maybe not Konqueror) to support the KHTML.

As you have already said, Blink is based on WebKit, which is based on KHTML. You see Blink ist the ongoing further development of KHTML. So why do the work again ?


Bookmarks



Who is online

Registered users: Bing [Bot], blue_bullet, Google [Bot], Yahoo [Bot]