Discover also handles Flatpaks, Snaps, firmware, and user-installed KDE add-ons (Get Hot New Stuff). And probably more in the future.
Announcement
Collapse
No announcement yet.
KDE Will Now Let You Easily Disable Offline Updates, More KWin Crash Fixes
Collapse
X
-
Originally posted by alcalde View Post
Thanks. This looks as bad an idea as when they had their own web browser.
- Likes 1
Comment
-
Originally posted by mcloud View Post
If KDE didn't made their own web browser back in the day, we wouldn't had KTML .Which means no Blink engine, no Chrome, no Safari and also no Edge (in its last incarnation)
Comment
-
Web got complex and there is even fewer ppl to work on complex stuff like browsers. I don't remember getting crashes, just different rendering or being slower, but maybe it's just the choice of site one uses, never tried like any modern game on it ever
- Likes 1
Comment
-
Originally posted by alcalde View Post
That's what some people tried telling me six years ago too before Konquerer was killed off. But if Konquerer was the progenitor of Chrome, Safari and Edge... what the heck happened? Konquerer ended up slow, broken, and prone to crashing at the slightest hint of Javascript.
As for the offline update, this is just one way to update, you don't have to use discover to update and even if you want, you can disable them with one click.
However I agree that for the common user it is useful, because after an update the user should at least restart the session, but there are few who do it, otherwise it is possible to have system crashes, as the system is in an inconsistent state . This also results in the reporting of non-existent bugs.
Comment
-
Originally posted by Charlie68 View PostIt would be enough to look reality in the face, there is no browser today that can compete with Chromium and its derivatives or Firefox.
There are 3 major groups of browsers today as a web developer you need to support. The blink engine based ones that are you Chromium and derivatives then you Gecko based ones that your firefox and relatives then you Webkit ones that are your Safari and relations that is all you iOS devices as blink and gecko don't work on iOS that is quite a large user base.
Originally posted by Charlie68 View PostSo why should KDE waste time on a browser that two cats will use?
Konqueror is KDE's Webbrowser and swiss-army-knife for any kind of file-management and file previewing.
Because kde browser is not just a generic web browser. Also if you read more you find it dual engine as in khtml and webkit for html stuff. The webkit form means its in with the iOS browsers. Yes Kouqueror still has a ftp client that firefox and chrome are both losing has support for other internet protocols that firefox and chrome never have supported.
My problem with Konqueror is how do you put a correct security policy around the beast. For number of features shoved in a single program Konqueror is well and truly up there.
Comment
-
Originally posted by oiaohm View PostThis is not quite right.
There are 3 major groups of browsers today as a web developer you need to support. The blink engine based ones that are you Chromium and derivatives then you Gecko based ones that your firefox and relatives then you Webkit ones that are your Safari and relations that is all you iOS devices as blink and gecko don't work on iOS that is quite a large user base.
Konqueror is KDE's Webbrowser and swiss-army-knife for any kind of file-management and file previewing.
Because kde browser is not just a generic web browser. Also if you read more you find it dual engine as in khtml and webkit for html stuff. The webkit form means its in with the iOS browsers. Yes Kouqueror still has a ftp client that firefox and chrome are both losing has support for other internet protocols that firefox and chrome never have supported.
My problem with Konqueror is how do you put a correct security policy around the beast. For number of features shoved in a single program Konqueror is well and truly up there.
Comment
Comment