That's why I said Wayland and the modern desktop in general.
> So you are fine with X server takes care of most of the stuff, but not fine with wl_roots do the same thing?
You're kind of right: conceptually it's not much different, except that a wm is not a full-fledged server, but simply a client talking to the X server. If I'm sloppy and my wm dies, it's not going to take down the whole desktop with it, contrary to a Wayland compositor.
> A base graphics API based on drawing primitives like the original X, SVG or Cairo, rather than just bitmaps.
Of course, but the rendering happens on the client (with client-side fonts, images, etc.) instead of the server, which makes the protocol use a lot of bandwidth.
