Citation? X11 window managers are decoupled from the rest of X and the OS by well-specified protocols.
That compositing manager also needs to handle input
Oh yes, I forgot how Wayland couples the WM to the OS as well.
Wayland handles software modularity by providing a library for use by prospective compositing managers. Moving the compositing manager into a separate process from the thing actually doing the rendering does not add a useful form of modularity.
1) Can you point me to an API specification for Wayland compositor libraries? If not, it's not decoupled.
2) Can one switch window managers without restarting the compositor (and thus losing window state) with Wayland? If not, it's missing a "useful form of modularity" provided by X11.
Citation? X11 window managers are decoupled from the rest of X and the OS by well-specified protocols.
That compositing manager also needs to handle input
Oh yes, I forgot how Wayland couples the WM to the OS as well.
Wayland handles software modularity by providing a library for use by prospective compositing managers. Moving the compositing manager into a separate process from the thing actually doing the rendering does not add a useful form of modularity.
1) Can you point me to an API specification for Wayland compositor libraries? If not, it's not decoupled.
2) Can one switch window managers without restarting the compositor (and thus losing window state) with Wayland? If not, it's missing a "useful form of modularity" provided by X11.