I'm also not filled with confidence by posts like this[1], which confirm that Wayland was still deeply broken in many ways just in 2024. Two years is not a short amount of time, but given it took Wayland 10+ years to be anywhere close to usable for desktop usage, I'm not placing my bets on the pace having gone up so fast that long-standing issues are solved yet. That post takes somewhat of an extreme position, but kernel of truth is that it breaks a lot of things, many of which apparently still aren't solved.
This post[2] has a better outlook I believe. I.e. that things are broken today (since it is for accessibility), but that there is real potential and that it can be fixed. It just has to be done. Shame that doing that is hard and that accessibility ends up taking a back seat.
[1] https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d...
[2] https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-d...
For all the noise about the "unix philosophy" and systemd being too all encompassing, Wayland went the other way and people still aren't happy.
I'm yet to see someone complain about systemd and Wayland in the same comment, or even comment chain for that matter, which does scan, given how they have diametrically opposed philosophies to things. The Venn diagram of people who dislike and Wayland and systemd are probably not quite two separate circles, but I can't imagine the overlap is very large. I actually like systemd a fair bit, since it seems to do its job pretty well. I've seen people have problems with it, but most of the opposition to it are on philosophical grounds rather than about matters of functionality, whereas with Wayland, the opposite is the case.