xwayland is still being actively developed, xserver is in maintenance mode, which isn't a bad thing, especially for such an old, somewhat mature tech, but being

xwayland is still being actively developed, xserver is in maintenance mode, which isn't a bad thing, especially for such an old, somewhat mature tech, but being actively developed is something else in my understanding. And one just cannot do away its architectural problems, which was the reason for a "from scratch with (some) hindsight" approach in the first place, under which new approaches like Wayland and mir got developed. > It does what I need. If the features of neither of those fit your use cases: great, be happy and keep using what works for you. But I, for one, like to have no tearing anymore, no random apps just stealing my keyboard input or clipboard content, having a more efficient way to operate on (frame) buffers, having active development for new tech features like HDR and that all while still running xwayland for 100% x11 compat; you cannot do the reverse, at least while not also getting the same features. So, I really like wayland as it gives people the possibility for better security/sandboxing and new features while I can just run x11 apps fine. > From my perspective, Wayland is like btrfs The same with btrfs, as RAID0/1/10 its just nice and stable since forever, its architecture is seemingly just a bad fit for RAID5/6, the single possible problematic part since a while, CoW and rebalancing are really nice to have on a server with important data. Multiple FS catering to different requirements are there for a reason, and not everyone needs to use every type of FS to give it a reason to exist...