Honestly, I was never convinced that concentrating all developer effort onto Wayland was the best idea. Wayland seemed like a massive over-correction from X11, where the protocol and core were "simple" in comparison to X11 which did everything. Being simple, by itself, is not a virtue -- Wayland basically forced all the essential complexity of the problem to the compositors (a la Waterbed theory of Complexity [1]). Given there are so many compositor implementations, they essentially end up reinventing the wheels all the time. This is a bit better now with wlroots, but unfortunately, the ecosystem is already fragmented. I'm not saying X11 is superior to Wayland or vice-versa, but frankly I would be surprised if we couldn't improve X11 if it got 0.1% of the amount of effort collectively gone into Wayland.

I would highly recommend reading through some of these blog posts who expound upon the problems of Wayland more eloquently than I can [2,3,4].

[1]: https://en.wikipedia.org/wiki/Waterbed_theory

[2]: https://dudemanguy.github.io/blog/posts/2022-06-10-wayland-x...

[3]: https://pointieststick.com/2023/09/17/so-lets-talk-about-thi...

[4]: https://utcc.utoronto.ca/~cks/space/blog/unix/WaylandTechnic...