I would say that this is not really true. One of the biggest complaints with Wayland has been the lack of network transparency. Waypipe came along and added tha

I would say that this is not really true. One of the biggest complaints with Wayland has been the lack of network transparency. Waypipe came along and added that outside the compositor. The article itself mentions pipewire adding functionality. You can still write small focussed tools. With compositor libraries like wlroots, swc, and Louvre appearing, it is no harder to write a Wayland compositor than an X11 window manager. It looks like it will lot be long before it is easier. And while few ever attempted making alternatives to Xorg, multiple parties have created their own Wayland compositors. You can say that nobody bothered because Xorg was great but clearly writing a Wayland compositor is far easier. The article says multiple compositors is a problem. I see that as a benefit although I certainly get that it will be a pain for app devs. At least, it will be that way until the ecosystem matures and the bad across stand out more. Compare the logic of what is being said here with the web. Should we all celebrate when Chrome wins the browser wars. Clients will finally have just one environment to target instead of having to deal with how multiple instances implement the standard. Oh wait, over there we think that multiple browsers is a good thing. Why not on the desktop?