From a programming point of view, do not make one of the biggest mistakes of x11: keep wayland code statically linked, do not create zillions of client librarie

From a programming point of view, do not make one of the biggest mistakes of x11: keep wayland code statically linked, do not create zillions of client libraries and then depends on their ABI. Wayland is so simple anyway, that would be kind of ... The only "fake" exception is xkb, since it is not part of wayland, client-side keyboard key symbol resolution has to go thru libxbkcommon ABI because you don't know where the data files are, unless a standard environment variable is defined, and you cannot be sure the format of those data files would be working with your code, unless the format and file hierarchy of those data files is simplified and posix-ized/iso-ified for forever namely _without_ versioning. Since I play games on elf/linux, my main issue is the steam client without wayland support, not even a wayland->x11 fallback (they don't even have a vulkan->GL->CPU fallback, not to mention the 32bits code...)