https://bugs.kde.org/show_bug.cgi?id=436318
--- Comment #253 from [email protected] --- (In reply to Lassi Väätämöinen from comment #252) > (In reply to Brian Kaye from comment #251) > > I still do not understand that since X11 solved the session restore problem, > > why could that solution not be imported into Wayland or whatever the session > > restore process is now. > > I guess the short answer is something in the lines of: because Wayland was > not meant to be the same bloatware as X11 is. And adding all the features in > it would make it as inflexible as X11 was. To compare one of the most productivity-enhancing features of modern desktops with "bloat" is somewhat beside the point, I'd say. And implementing such a key-feature surely wouldn't have made wayland "inflexible". That's ridiculous. Thus, another "short answer" might be: the Wayland-devs didn't care or weren't up to the task - despite a blueprint (XSMP) that's been around for more than 30 years. And BTW: if I were a QT- or KDE-developer, I'd be _very_ cautious to point fingers at others when it comes to "bloatware". I hope you're wise enough to refrain from asking for hard data. > > But as Nate has already mentioned (I guess several times), the bug comment > section is really about techincal discussion regarding the actual bug, not > general. So I'd suggest moving the general dicussion to > https://discuss.kde.org/. Had KDE-, QT-, or wayland-devs solved this problem after 4 weeks or 4 months or even a year, there wouldn't be a discussion at all. But after more than _4 years_ I guess some perhaps not so technical - but nevertheless mostly constructive - comments are quite understandable. And in case you have opened a thread for this topic on https://discuss.kde.org/: could you post the link, please? Thanks. Anyway - it's good that there is progress in this matter and that we've been informed about it. Thanks. -- You are receiving this mail because: You are watching all bug changes.
