[zajio1am]

> So you are fine with X server takes care of most of the stuff, but not fine with wl_roots do the same thing?

There is big difference in responsibility w.r.t. users in Xserver vs wl_roots case.

In the X11 case, relations are:

wm - user - X11

(Users choose to use Xserver and WM independently, if there is a bug in Xserver, then it is outside of responsibility of WM developers.)

In the Wayland case, the relations are:

user - wm/compositor - wl_roots

(Users choose wm, wm developers choose to use wl_roots to implement wm features instead of doing it themselves, but that is just internal implementation issue of that wm and wm developers are responsible for wm behavior/bugs including ones inherited from wl_roots.)

[samus]

That's actually a good thing! If the bug is in X, then the WM developers are powerless against it. If it is in wlroots, then something can be done about it. Since it's a library, it should be possible to roll out a bugfix at a faster pace than the X server. Worst case you fork and bundle wlroots, leave behind a pull request to the main project, and move on.