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.

  • DarkMetatron
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    17 days ago

    As a disclaimer: I really like Wayland and use it as my daily driver for months now with KDE/Proton.

    Now my answer, based on my best knowledge:

    Because there is no real Wayland to implement, the base Wayland protocols are extremely bare bone and most of the heavy lifting is done by all the different wayland compositors like hyprland, plasma, Mutter, weston, wlroots, gamescope so as a developer you don’t have one target to program against (X11) but lots of different wayland implementations and those are not always doing things the same way or providing the identical interfaces/API or have the same level of features.

    On my system is at least one wayland only program that works absolutely fine when started in a wlroots environment but crashes (reproduceable on different systems) with a segmentation fault in Mutter or Plasma.