3 ms·
One does not simply write a window manager in Wayland. In Wayland the display server and window manager are one program, called the compositor, which means the
by bitwize 4y ago
One does not simply write a window manager in Wayland. In Wayland the display server and window manager are one program, called the compositor, which means the X11 architecture of having a separate window manager is now deprecated. (Insert Daniel Stone talk here about how this is the superior choice and the go-forward solution because people who know a lot more about the graphics architecture than you said so, that's why.)
Wayland's architecture in general is completely different, so you don't so much port a WM as you do rewrite it as a Wayland compositor. There are libraries like wlroots that help with this task but it is not straightforward.
- kaba0 4y agoI do know that, but I don’t see how exposing the same functionality as the X11 bindings do for AwesomeWM as too hard of a problem, especially that I believe the majority of the work is done on wlroots already. Perhaps I just don’t know enough about Awesome.
- michaelmrose 4y agoMore to the point the choice isn't between writing one or the other it's between doing 1 unit of work to maintain/fix bugs and doing 1000 units of work to start over potentially for little perceptible benefits.