Going all-in on a Wayland future
blogs.kde.org
Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.8 release will be Wayland-exclusive! Support for X11 applications will be fully entrusted to Xwayland, and the Plasma X11 session will no longer be included.

cross-posted from: https://lemmy.world/post/39342270

Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.8 release will be Wayland-exclusive! Support for X11 applications will be fully entrusted to Xwayland, and the Plasma X11 session will no longer be included.

    • brucethemoose@lemmy.world
      37·
      1 day ago

      Apparently, this is hardly hyperbole. For example: https://bugs.kde.org/show_bug.cgi?id=377162

      Talk about arrogance. In the window paradigm, only a few desktops ever REQUIRED a similar look and feel for all windows. Apple was the worst offender for that. I suggest that if Edmundson wants a similar look and feel, he should go get himself a Mac and stop mucking up KDE.

      From a quick look at the proposed patch - and obviously without having the full picture - it’s true that it would add some complexity. But it’s code for the sake of people’s convenience, not the other way around, right? IMHO, as long as:

      • shading is off by default,
      • users get a clear message about limitations and SSD/CSD complications before enabling it,
      • the implementation doesn’t introduce impossible-to-maintain logic and limits some weird edge cases like resizing a shaded window, then it’s worth doing.
      • majster@lemmy.zipEnglish
        3·
        7 hours ago

        So there is no shading on KDE Wayland? This feature works in Labwc. Death by thousand papercuts…

        • brucethemoose@lemmy.world
          1·
          6 hours ago

          I suppose not. Not yet.

          I know people are particular about WMs, but having to minimize a window vs keeping the window decoration in place seems like a… very minor distinction.

          Is the use case rearranging a ton of windows? Something like that?

          • majster@lemmy.zip
            4·
            5 hours ago

            If I have to cross reference info from two windows I like to have one floating and always on top. In that case its nice being able to roll-up the window to see whats behind it. Minimizing would be similar but it feels more permanent than rolling up.

          • Peasley@lemmy.world
            2·
            5 hours ago

            RE: use case

            It’s really nice to be able to see the whole titles. A vertical panel cuts off most text, so you just have a bunch of icons when you minimize. if multiple windows are from the same app it’s confusing.

            If you use a horizontal panel you have a bit more room, but a significant amount of text is still cut off, and the panel fills up quickly.

            Even with as few as 6 windows open (lets say two browser and three file manager, and a terminal) minimizing is a mess. I find it better to just leave the window bar somewhere visible and shade it, since i can read all the text on my window at a glance. Combined with “keep above others”, you can get a really nice way to quickly refrence something infrequently while you do most of your work in another window.

            A more typical workflow for me is 1-4 windows of a pdf reader, 1-3 file manager windows, 1 browser window, and 1 terminal window. It’s just easier to keep it all organized with window shading.

            I find it much faster than a bunch of alt-tabbing, or playing hide and seek with the panel just to get a specific two PDF windows up side by side for a second