Wayland seems ready to me but the main problem that many programs are not configured / compiled to support it. Why is that? I know it’s not easy as “Wayland support? Yes” (but in many cases adding a flag is enough but maybe it’s not a perfect support). What am I missing? Even Blender says if it fails to use Wayland it will use X11.

When Wayland is detected, it is the preferred system, otherwise X11 will be used

Also XWayland has many limitations as X11 does.

  • nexussapphire
    link
    fedilink
    English
    arrow-up
    1
    ·
    24 days ago

    This whole argument ignores xwayland and the fact that new features are added as a standard of Wayland literally every day.

    For as long as xwayland is supported you can use your old apps. Wayland actually supports different window icons for multi window apps. But Wayland has always supported window icons, kde just had an annoying bug they finally fixed. Chromium and electron apps kinda just didn’t support window icons very well in wayland for a while.

    For accessibility, it’s been broken on Linux for literally years but there’s an active effort to make it better and more universal than it ever could have been on x11. The effort of building a fully featured accessibility stack is being led by the gnome team with help from the free desktop organization and kde.

    This is my last response, this conversation isn’t going anywhere anyway. I’m not the one transitioning the Linux world to Wayland, I don’t see why you could blame me for it anyhow.