[comex]

By the same token, if, as a developer of software, you presume that it’s incumbent upon people spending their own money to buy hardware that caters to your software design, one should not feel bad if users ignore your project and use alternatives that are compatible instead – namely X.

If Wayland developers truly do not care about adoption of their software, then that’s fine. But it means that UI frameworks which do care about adoption will have to continue to support both X and Wayland as backends indefinitely, increasing complexity. That’s okay for now, since removing X support would be a long way off in any case. But if enough years go by without at least a plausible route towards being able to remove it in the future, they may eventually decide to address the complexity issue by dropping Wayland instead.