Linked by Thom Holwerda on Thu 2nd Jul 2009 12:19 UTC
Thread beginning with comment 371305
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
This post started it all:
http://www.kdedevelopers.org/node/3995
I have to agree with some comments that the KHTML devs are actually hurting KDE as a whole.
Complex web apps will never work in KHTML and giving people the illusion that that might change is bad. KHTML is a dead end.
I have to agree with some comments that the KHTML devs are actually hurting KDE as a whole.
Complex web apps will never work in KHTML and giving people the illusion that that might change is bad. KHTML is a dead end.
Complex web apps will never work in KHTML and giving people the illusion that that might change is bad. KHTML is a dead end.
You can't blame KDE for trying to build a full desktop environment with a web browser and everything, but you can blame the distributions, they pick the defaults for users.






Member since:
2008-12-26
There are several blog posts about the khtml/webkit saga recently, which you saw if you read planetkde:
http://planetkde.org/
Here they are for the lazy:
aseigo: http://aseigo.blogspot.com/2009/07/webkit.html
Actual khtml dev: http://vtokarev.wordpress.com/2009/07/01/being-a-khtml-developer/
(that one makes an interesting point - why should he be working on webkit for free, when there are so many paid developers doing the same thing for pay?)
http://blog.gwright.org.uk/articles/2009/07/01/qtwebkit-vs-khtml-ag...
http://darktears.wordpress.com/2009/06/30/my-only-blog-post-about-k...