> more than just culture. The Wayland protocol has made the compositor, window manager and window server concepts a single thing I realize that any implementat

> more than just culture. The Wayland protocol has made the compositor, window manager and window server concepts a single thing I realize that any implementation of the Wayland protocol must of necessity involve compositing somewhere in the stack simply due to the nature of the protocol itself. And I also realize that all current Wayland "compositors" happen to roll all this functionality into a single monolithic implementation. But I honestly don't understand what's stopping someone from implementing a modular Wayland display server which you plug a conforming compositor into (with the caveat that, unlike X11, such a module would not be optional). Is there some technical issue I'm unaware of that would prevent a standalone display server implementation speaking the Wayland protocol from delegating all the necessary behavior via indirection?