this post was submitted on 26 Jan 2026
108 points (85.1% liked)
Linux
11481 readers
568 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It is a different ecosystem. It requires time to mature and yes, you have to migrate to it in order to use it.
Moving to Wayland was a bit like moving to a different operating system from an application point of view. The toolkits made that reasonably easy for most apps but they really do not help much if you are the window manager.
So yes, compositors had to be built. This was easy enough for the big projects like GNOME and KDE but a bigger ask for smaller players. But there are lots now: GNOME, Plasma, Hyprland, MangoWC, Niri, COSMIC, Budgie, LxQT, LabWC, Wayfire, Sway, DWL, River, Wayland Maker, etc. I am sure there are many more I don’t know or forgot. There will be lots more.
And yes, a Wayland compositor is a bit like the X server and window manager combined. So, they are harder to build. Except libraries have appeared to do that. There are wlroots, Smithay, aquamarine, Louvre, and SWC. There will be more. So, a Wayland compositor is not really that much harder anymore. And it will get easier.
The XFCE project is just starting a Wayland compositor project now. It will be built mostly by a single developer. They think they will have a dev release in a few months. They are using Smithay.
Building the Wayland ecosystem took time. But we are basically there. And it is only going to get bigger and better.
The transition would have been a lot less acrimonious if it had been attempted after wlroots was usable, or if people working on Wayland itself had made an effort to write something like wlroots.