Which one? The Gnome Wayland, the KDE Wayland, the xroots wayland, Weston, or one of the others? Each one is an independent implementation of a Wayland compositor, with a differing, incompatible set of extensions.
X11 was a single, pretty janky implementation. Wayland is the worst of both worlds -- it's cleaned up a little, but it's still kinda janky. In exchange for a little bit of cleanup, mainly around bitmap fonts, it's no longer a unified protocol.
And to top it off -- it kept the worst part of the X11 protocol, the XKB extension, but got rid of input handling entirely, which means that every platform needs to reach for platform specific code to implement reading from the mouse and keyboard.
If we're hypothesising a perfect world, ideally they standardise some way of sharing framebuffers between programs into Wayland. I suppose maybe they already have I gave up on the ecosystem in the early 2020s. That seems like it should be long enough ago now that they've got even advanced features like screenshots under control and rolled out.
Sure, but I don't see a world where keeping X11 alive, in addition to all of this, makes anything better or easier, for anyone in the medium to long term.
If, as an application developer, you target X11, you have a program that will work on Linux and BSD with all desktop environments. It'd even work on Wayland via Xwayland. If you want to use it on other OSes, it's less smooth, but also working on MacOS via Xquartz, and Windows via Xming. There's even an X11 compatibility layer for Haiku (Xlibe).
With Wayland, you don't even get compatibility with Gnome and KDE. You need conditional compilation to get mouse events if you port to FreeBSD Wayland.
For the medium term, if your goal is to reduce fragmentation, X11 is the portable target, even if you use Wayland.
It makes things a lot better for me, for one, and clearly there are more of us. You may not think it matters, and that's fine, but X11 won't go away because there are enough of us that won't let it.
X11 was a single, pretty janky implementation. Wayland is the worst of both worlds -- it's cleaned up a little, but it's still kinda janky. In exchange for a little bit of cleanup, mainly around bitmap fonts, it's no longer a unified protocol.
And to top it off -- it kept the worst part of the X11 protocol, the XKB extension, but got rid of input handling entirely, which means that every platform needs to reach for platform specific code to implement reading from the mouse and keyboard.
Yay.