Wayland. It comes up a lot: “Bug X fixed in the Plasma Wayland session.” “The Plasma Wayland session has now gained support for feature Y.” And it’s in the news quite …

Wayland. It comes up a lot: “Bug X fixed in the Plasma Wayland session.” “The Plasma Wayland session has now gained support for feature Y.” And it’s in the news quite a bit lately with the announcement that Fedora KDE is proposing to drop the Plasma X11 session for version 40 and only ship the Plasma Wayland session. I’ve read a lot of nervousness and fear about it lately. So today, let’s talk about it!

  • merthyr1831@lemmy.world
    1·
    1 year ago

    Maybe a while ago that was true. But there’s so much cool stuff that KDE devs are spearheading with Wayland.

    For example, You’ll be able to reboot the window server without ending your session and losing your app state! They’ve demonstrated being able to swap between GNOME, KDE, Sway, and other WMs without logging out or crashing apps. This could also be used for swapping active GPU configurations without relogging, which would make Gaming laptops way less shitty to use.

    Wayland can also store window state to disk, which isn’t possible on X11. Another useful feature that could allow for more fluid hibernate and reboot behaviour.

    Touchpad gestures! You need a lot of dev effort to get them working on X11 but on Wayland it’s very fluid.

    Wayland is also partly why there’s been new effort to standardise the desktop experience on Linux with stuff like XDG.

    For the end user, X11 is fine. You don’t need to particularly care how your windows are drawn. As an app or desktop dev you’ll be way more empowered to build a next generation desktop experience with Wayland, in a way that X11 just wasn’t able to support because of its underlying design.

    But that’s also why the change can’t come from begging end users to migrate: we have to rely on distros dropping support for X and making Wayland the default.