Plasma developer David Edmundson demonstrates how a desktop using Wayland, Qt6 and KWin can recover from a catastrophic crash as if nothing had happened.
... And can provide a way to save the state of an application to disk, stopping the app in its tracks and removing it from memory, so that later you can restore it just where you left off.
@kde Oh my god, this is so cool! Especially like someone said for mobile linux. A lot of the nuances are a bit over my head, can someone explain the downside that Otte in the gitlab issue tracker is saying in layman's terms?
This would be amazing for games that take forever to load. When you want to exit the game just save it’s state to the disk, and the next time you want to play it just resume and boom! Instead of waiting for 3 minutes, you can play it almost immediately.
I think there may be more fundamental issues to be dealing with. I found Gnomes tracker3 service to be stuck in a loop permanently eating cpu when installing kde on Ubuntu LTS 22.04. I had to chmod 000 gnomes tracker3 binaries as systemd was impotent. An average user would have degraded KDE expereience due to Gnomes fault!
@kde@kde
> For X11 this was unfixable; clients relied on memory stored by the Xserver, they made synchronous calls that were expected to return values, and multiple clients talked to multple clients.
time for X11 bouncer, X11 is network transparent ✨
@kde@kde Very cool. Here’s hoping to see this in @gnome one day too.
PS. I’m sure you’re aware of it but, just in case, the window positions/dimensions appear to be lost on the restart. (An issue I have on GNOME too whenever it returns from suspend.)
@nora
If you don't fix it, then close it.
But you don't dare do that either, do you?
And one could also argue differently:
the KDE developers don't give a shit what the users want, because they only want to do their own stuff.
Ignoring a bug with almost 500 comments and insulting the users (you're not the first to get mad at me for this) shows me in any case: you do your thing and don't care about the userbase.
This way of developing is the reason why KDE never made it to the Company desktops.
@aschnefuenfzehn@nora Oh... They care a lot about the users
After all these volunteers were once just users. But that doesn't that they will impliment every feature every user wants. Yeah, even o
If the feature request has 500 comments.
And companies most definitely does use KDE. NASA, LERCS, LIGO, CERN, ALBA Synchtron - and lot of scienty places, in building the first Avatar film and BlueSystem also uses KDE Apps and Plasma. I feel like I missed something - oh yeah - Valve.
a) This is not a "feature request", this is a bug
b) Nate Graham himself has promised that the bug will be fixed (in case you haven't read the 500 bug reports)
c) KDE is not only developed by volunteers.
See: https://curius.de/2021/05/open-source-entwicklung-freiwillige-oder-firmen/
KDE has unfortunately not disclosed the affiliation of its developers,
but due to known sponsorships, e.g. by blue systems, one can assume that not all are volunteers here either.
@whjjackwhite@nora
The lack of transparency leads one to suspect that other companies also pay permanent developers. Among others Trolltech and SuSE.
d) The "companies" you mention are for the most part not companies but scientific institutions. You can quickly compile something there if it doesn't work. This is not the case with companies that have to earn money.
e) The KDE I find at Cern has the version number 3.
Look, it comes down to the fact that as far as I know, the vast majority of KDE developers are volunteers with their own lives. There was a given explanation for why it hasn’t been fixed, it was complicated code that was hard to maintain. Its not as simple as someone writing code to reimplement the feature, the feature also needs to be maintained which is a lot of work for a project with so few resources compared to proprietary projects that can afford to pay hundreds of full time developers.
People requesting that feature to come back are just kind of rude about it, skipping out on basic manners. Personally if I were a KDE developer I wouldn’t want to work on a feature after all that.
Compositor handoff to switch between desktops looks legendary! I super hope something like that becomes stable and officially supported somewhere, it would be so fun to use
@kde I'm very interested on how #gtk will handle this, especially for very long running applications such as IDE's or Emacs.
Currently GTK commits suicide for you if it looses the connection to the Wayland display server by calling _exit().
… And can provide a way to save the state of an application to disk, stopping the app in its tracks and removing it from memory, so that later you can restore it just where you left off.
Add comment