I think there is a subtle difference here in that the X server was a target that things were built on top of. Wayland is one component of a larger ecosystem has the same goals as X.
It is feasible to just run X and have a passable desktop experience. I don't think it is feasible just running a vanilla Wayland compositor, it needs to support a bunch of non-Wayland technologies and extensions to be useful. I'll point at Pipewire as the major example. And the kernel plays a more active role than X11 was designed to handle.
So it is similar to Python 2->3, but if major parts of the standard library were being shed. Given the screenshot situation, I'd say it was a Python 2->3 except the core team insisted that printf among other things be implemented outside the language core. Wayland explicitly doesn't cover the same design space as X11 and in most cases that is intentional and an improvement.
I think that the switch will happen when somebody advances Weston (or any other compositor that has a single-app full-screen mode) so that running Xfce on Xwayland on Weston becomes possible and indistinguishable from Xorg.
It is feasible to just run X and have a passable desktop experience. I don't think it is feasible just running a vanilla Wayland compositor, it needs to support a bunch of non-Wayland technologies and extensions to be useful. I'll point at Pipewire as the major example. And the kernel plays a more active role than X11 was designed to handle.
So it is similar to Python 2->3, but if major parts of the standard library were being shed. Given the screenshot situation, I'd say it was a Python 2->3 except the core team insisted that printf among other things be implemented outside the language core. Wayland explicitly doesn't cover the same design space as X11 and in most cases that is intentional and an improvement.