>> Xorg [...] allowed arbitrary stuff to build on top.
> Same as wayland.
No, because Wayland puts everything on the compositor. X11 let me run the same screenshot tool on GNOME, KDE, and dwm. In wayland, the only way to support GNOME, KDE, and sway is to add multiple backends. In X11, window managers and compositors were interchangeable and orthogonal; in Wayland, the "window manager" is subsumed into the compositor (now mandatory), which is the display server. I really like keynav. AFAICT, implementing an equivalent in Wayland requires integration into each compositor. There's still a monolith, but it got moved up the stack to a place where it prevents piecemeal environments.
> Same as wayland.
No, because Wayland puts everything on the compositor. X11 let me run the same screenshot tool on GNOME, KDE, and dwm. In wayland, the only way to support GNOME, KDE, and sway is to add multiple backends. In X11, window managers and compositors were interchangeable and orthogonal; in Wayland, the "window manager" is subsumed into the compositor (now mandatory), which is the display server. I really like keynav. AFAICT, implementing an equivalent in Wayland requires integration into each compositor. There's still a monolith, but it got moved up the stack to a place where it prevents piecemeal environments.