Why Firefox is not a good choice of browser for a KDE/Plasma-based product

Eli Wapniarski eli at orbsky.homelinux.org
Sun Mar 30 14:44:40 UTC 2014


So in the end, the choice comes is between a browser that doesn't work as well as it 
should but looks like it belongs (on many different fronts), or a browser that works the 
way it should but doesn't quite integrate.

hmmm.

Sounds like the main desktop developers (ie gnome / kde / qt). Have not come up with 
an adequate solution for web browsing. That's why the vast majority of us use firefox 
or google chrome or both. KDE provides a way to integrate the look and feel of KDE 
onto the gtk based apps.

Again... I for one would be using Firefox as my main browser regardless and since it is 
packaged with Fedora.... Maybe...just maybe the hands should go up in the air and we 
should say "oh well that life" and provide Firefox because well... thats the browser 
people use.

Eli

On Sunday 30 March 2014 13:32:14 Kevin Kofler wrote:
> Eli Wapniarski wrote:
> > there. I miss boasting about the speed and versatility of what was the
> > fastest lightest and most versatile browser on the planet until the team
> > started to adapt Safari (Mac changes) into Konqueror.
> 
> The WebKit fork has indeed made many things worse, especially when it got
> then ported (back) to Qt, absorbing many of the KHTML developers and leading
> to 2 competing HTML engines in KDE. WebKit's code is also much less cleaner
> than KHTML's. But these days, KHTML cannot match WebKit's JavaScript
> performance (on sites massively and unnecessarily abusing JavaScript) nor
> its support for the fancy newfangled HTML 5 "features" websites are
> (ab)using all over the place for no good reason. So we have to work with
> QtWebKit.
> 
> And what's worse: now the same thing is happening all over again! Blink has
> been forked from WebKit, it too is getting ported to Qt (QtWebEngine),
> absorbing the QtWebKit developers, and the code is even worse than WebKit's.
> (Sure, they "cleaned up" the #ifdef mess, but they did that by hardcoding
> the worst possible options: FFmpeg (with its patent issues and its
> monolithic structure that doesn't allow easily working around them) for
> multimedia, V8 (which is JIT-only and has no portable interpreter fallback)
> for JavaScript, etc. And they added more bloated mess of their own.)
> 
>         Kevin Kofler
> 
> _______________________________________________
> kde mailing list
> kde at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/kde
> New to KDE4? - get help from http://userbase.kde.org


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/kde/attachments/20140330/b66bd72d/attachment-0001.html>


More information about the kde mailing list