2 ms·
>There's a lot griping about how Wayland isn't a monolithic server Implementation detail. >how different compositors have to reimplement base capabilities Im
by charcircuit 3y ago
>There's a lot griping about how Wayland isn't a monolithic server
Implementation detail.
>how different compositors have to reimplement base capabilities
Implementation detail
If people wanted they could make a monolithic server. They could make window management happen by a different process that could be swapped out.
- tadfisher 3y agoThe problem there is that the Wayland protocol family is not tolerant of dropping events or buffering them indefinitely, so there is no benefit to an X server-like architecture where you can transparently restart or replace the compositor. You're welcome to try, of course, but there are an incredible number of scenarios that break clients; one off the top of my head is if the mouse cursor creates a client tooltip by hovering over some GUI element, then leaves that region while there is no compositor to handle the mouse movement events. You're going to end up in a world where you're synthesizing fake events to "reset" the state of clients, and this is dragons-at-the-edge-of-the-map territory. I wish Wayland was architected around a state-synchronization model instead of being event-driven. It'd be extremely difficult to port client toolkits and would ultimately fail to attract adoption, of course, but you'd end up with a more resilient system overall, and one that could be a bit more implementation-agnostic.
- eternityforest 3y agoThe problem is we have to use Wayland now, but the ecosystem isn't quite at X11 levels. Most documentation and tutorials are X11. Wayland will probably be amazing like many of other technologies I've ever disliked in the past (Some of them still seem to suck though!) but right now it's still effectively brand new on the general user scene.