• rtxn@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    1 month ago

    My setup is two screens side by side and one above. KDE Plasma 6.1 can handle it without issues, and you can make panels on any screen.

    One of the most significant drawbacks of Wayland is feature fragmentation between compositors. Unlike the X11 stack of X.Org server + window manager + compositor, Wayland compositors have to implement all of Wayland in themselves. They have to serve as the display servers, plus manage window positioning, plus render the clients, and all of that within the confines of Wayland-protocols. Building a compositor is a massive task, which is why middleware like wlroots is such a big deal. It also means that WM-agnostic tools like xrandr and xdotool are more difficult, sometimes impossible to implement.

    Consider that Wayland is still heavily under development, and that new protocols have to be implemented by every compositor separately, and that the development of wayland-protocols is an ongoing fucking trainwreck – fragmentation is inevitable, and some compositors will not have the same functionality as others (GNOME being a particularly nasty sandbag). Similarly, things that don’t work as expected in one compositor might work perfectly fine in another.

    Right now I would consider KDE Plasma to be the most feature-complete compositor that is also beginner-friendly.