3 ms·

Is that really it? To cut off Xlibre at the pass? Because I am struggling to understand what the advantage of this over just using Xorg. I think 90% of desktop

Is that really it? To cut off Xlibre at the pass? Because I am struggling to understand what the advantage of this over just using Xorg. I think 90% of desktops will be Wayland as we leave 2027 (and more than 50% are now). I also think installing even Xwayland may be niche in 5 years. That said, Xwayland will be maintained by Red Hat until 2040 at least (minimum required for even RHEL 11). Xorg itself will be maintained intil at least 2032 and, by others, probably a decade or more after that. Xorg already uses lininput, DRI, KMS, and Mesa and shares a lot of code with Xwayland. So keeping it going will not be hard. So, what is the advantage of this approach over just using Xorg? I mean, if your goal is to run a legacy X11 window manager that is.

bitwize 1y ago
Again, Xwayland is Xorg, just with a Wayland DDX backend.If you check out the xorg-server source tree, you can build your own Xwayland with appropriate configuration. Beyond just doing an end run around nazi X forks, I think the idea here is to get everybody on Wayland by hook or by crook. The Xorg developers explicitly DO NOT want you to use Xorg, especially not with a direct hardware backend (even modesetting). Wayland is their solution for a much-needed replacement. and, going forward, aside from bugfixes Xwayland will be the only supported/maintained X solution. But really the idea is to keep Xwayland around only for legacy apps, so we'll probably see no new features or protocols added to Xwayland except perhaps to better integrate with Wayland desktops. Xwayland itself will be slated for deprecation and eventual removal from the latest versions of most major distros in the next ten years or so.