I’m not a fan of Wayland or a detractor of X. I’m not personally invested in either of them. I couldn’t care less what’s pushing pixels at my screen as long as it works. That said, what you need to know about Wayland is that the X.org devs mostly migrated to it en masse because they said X had hit an evolutionary dead end and couldn’t be dragged into the present, by the design of it. These were the people who were al…
I didn't know or care what was pushing the pixels on my Debian install, since it works. Being Debian, it could go either way: some of the desktop environments are committed to Wayland while other desktop configurations only work under X. (Incidentally, I checked. My setup uses Wayland.)
> It’s not like someone invented Wayland and shoved the X devs out of the way.
They sure make it sound as though X application developers are being shoved out of the way. I don't understand their argument though. Most modern software is built upon libraries that support either Wayland or X (assuming it has a GUI), so they should be blissfully ignorant of whether their application is running under Wayland or X. Most of the outliers are older programs that are built on top of libraries that haven't been updated for Wayland, but most of those programs will work under Wayland assuming that xwayland is installed. Again, there is no reason for the developer to concern themselves with the distinction between Wayland and X. That only applies to a relatively small subset of outliers that are interacting with X or the compositor directly. But you're not going to escape that problem, because you're either doing something unique or you are doing something you shouldn't be doing.