Wayland works perfectly, except for when it doesn't

Yeah, normally a . means the end of one idea and the start of another. You don’t take criticism well, I take it. And then labeling a comment as not criticism does nothing, I see.

Yeah, I didn’t understand most of that. In both systems, for most clients under X11 and all clients under the other, Compositing is completely controlled on the other side of the Client/Server IPC. There is nothing preventing a Wayland Server from implementing Compositing the same way X11 does, just use fork() and IPC instead of System or Soft Threads. The setup could even entail the Compositor connecting as a Wayland Client and then using a protocol extention. The reverse is also true, it wouldn’t be impossible to write a Xorg Module that take over Compositing and Window Management. In both Protocols it’s impossible for Clients to tell how many processes make up the architecture behind the Socket.

What part of I only care about the Technical Merits means I don’t care about the Technical Merits? Did you drop out of Logic 101.