Skimping on security and removing the thing that made Firefox at least as fast as the competition...
What options do we have now then?
Because I'm surely not going to skimp on either of those things.
What options do we have now then?
Because I'm surely not going to skimp on either of those things.
WebKit is KHTML, and since (as you say) it's the upstream rendering engine for many browsers, it makes sense for it to live in a "neutral" place; it's still an open-source project, and of course at this point it's had many contributions from outside KDE - which is how things are supposed to work.
If you prefer another WebKit-based browser then by all means use it - I've yet to find any that match Konqueror though. Just things like the integrated shortcuts from the context menu are better than anything else offers.
It's a shame this is happening at Mozilla. I was also quite shocked by their recent article to "safely return to shared memory between tabs", which I immediately thought was a bad idea.
Lo and behold, a mere week after that update, I found that Firefox was eating up my entire memory and making the PC perform poorly.
Shared memory is what made the old Firefox hang so much - I can't believe they thought it was a good idea. I've always believed Chrome's per process tab idea was brilliant, even if it uses a little more memory on average.
I still prefer the security benefits and stability of that architecture over Firefox randomly hanging and peaking in memory use due to memory leaks even if it can use slightly less memory on average.
https://news.ycombinator.com/item?id=19129086