Hot take: X11's separation of the window manager and the display server is really good and Wayland is taking a step backward by combining the two.

If KWin crashes or I need to restart it, I shouldn't lose EVERYTHING.

And yes, this does happen.

@IceWolf In fairness, the WM + display server can be separated in Wayland. There's nothing intrinsic to wayland to prevent that.

Wayland is just a protocol, not an application. It's down to the compositor implementor's decision whether the WM and display server run as separate process. It just happens to be simpler to implement them together.


@j Oh huh, had no clue you /could/ separate them like that!

Someone should write a display server everyone can plug window managers into. 3

@j ... course, that would require ANOTHER protocol soooo never mind.

@IceWolf Welp, ignore my last message. Seems like you figured it out for yourself.

@IceWolf The trouble there is that you now have to decide on a protocol that those WM's speak with the display server, and then need to get people to implement it.

@IceWolf @j there are a few library projects that are a bit like that, e.g. Wlroots and Smithay. I guess that in practice most types "non-mainstream" windows managers will be ported to/reimplemented on Wlroots.

Sign in to participate in the conversation

This instance is focused around the furry community, and is open to anyone interested in it. It's open to all fluffies and scalies ! ⚠️ We do not accept any form of sponsored content on our site. If you like meow, consider donating something via paypal or Liberapay