After more than forty years, everyone knows that it’s time to retire the X Window System – X11 for short – on account of it being old and decrepit. Or at least that’s what t…
X11 is a display server. Wayland is a presentation layer. Different goals. I have run graphical multi-seat systems using x11. Something like that will never be possible in the same way for Wayland because it is out of the design scope
Xorg is a display server. In Wayland, your compositor is the display server.
“I have run graphical multi-seat systems using x11. Something like that will never be possible in the same way for Wayland”
I have to give you this one. Wayland is not designed to be multi-seat. I do not know about “never” but you are right that multi-seat is a design difference.
X11 is a display server. Wayland is a presentation layer. Different goals. I have run graphical multi-seat systems using x11. Something like that will never be possible in the same way for Wayland because it is out of the design scope
X11 and Wayland are both protocols.
Xorg is a display server. In Wayland, your compositor is the display server.
“I have run graphical multi-seat systems using x11. Something like that will never be possible in the same way for Wayland”
I have to give you this one. Wayland is not designed to be multi-seat. I do not know about “never” but you are right that multi-seat is a design difference.
My mind goes to this project again: https://github.com/wayland-transpositor/wprs
But wprs only runs one compositor so it does not inherently address multi-seat. Support for that would need to be added.