That's not true for Wayland I think, Wayland is much closer to the Unix philosophy of doing one thing and doing it well: it is a (library implementation of a) local display protocol, and only handles input redirection and display configuration. It uses the kernel for device management, and puts clients fully in control of their own canvas through OpenGL.
It doesn't do output configuration, input management, application window drawing, font rendering, or remoting, all of which X did itself (although modern application rarely made use of that part of X). Those things are delegated to the kernel or to application libraries.
It doesn't do output configuration, input management, application window drawing, font rendering, or remoting, all of which X did itself (although modern application rarely made use of that part of X). Those things are delegated to the kernel or to application libraries.