It depends on your desktop environment and the applications, because the only compatible parts of Wayland are the dumbest "draw a rectangular window" and simplest input support (assuming your "WM" implemented the input right).
Essentially, what could depend on shared standards and implementations in X11, can't do so in Wayland, and there are two major forks when it comes to protocol extensions, as well as major fork between GNOME and everyone else on topic of Server-Side decorations.
It's evolution of the stance that started in early GNOME 2.x time, and crystallised with GNOME 3. Similar to how GNOME 3.8 was used to push systemd one everyone, similar to how they tried to push their own idea about input methods on everyone (since I don't use IBus, I don't know if they finally succeeded - fortunately UIM and XIM still work).
And yet, they have built the most popular desktop environment for Linux. To me, GNOME (on Fedora) feels more polished and visually consistent than Windows 10, which is impressive considering the massive imbalance of resources between those two projects. Would that have been possible if they listened to the zealots online who complain if they don’t support every possible configuration under the sun? I don’t think so.
It's not about supporting every possible configuration under the sun. It's often about not supporting the bare minimum that would make it a good environment, based on "know better" from people who have no relevant experience.
The IBus case is classic example - There was high-handed declaration that having one single global IME state is "easier" for users. The problem is when you regularly have to use languages that are incompatible in writing systems and input methods. Whether its one of the CJK or switching between one of the cyrillic variants and latin, life is much easier when you can have separate input state between let's say an Instant Messenger and your IDE.
For me, I recall the "canary in the coal mine" was when they refused (despite earlier promises and roadmaps) to re-implement certain things related to printing, again in a way that probably didn't bother the developers.
A similar case involves all the very deep integration with systemd, where they essentially declared that there's one Operating System under the Sun and its name is Fedora.
And it might feel more polished than Windows 10 on surface, yes. But then it's much less capable and the resources in Windows go towards things like not breaking people's software and behaviours.
Being better than Windows 10 is a low bar to clear, and doing so doesn't make your software not shit.
Honestly, the current state of mainstream desktop environments -- open source or proprietary -- is pretty awful with the exception of perhaps KDE and little ones like XFCE and LXDE. It kind of makes me glad I didn't hop on the GNOME train in the late 90s -- I could see the awful coming even back then -- and just stuck with a bare WM.
My personal conspiracy theory: the GNOME/Freedesktop/Red Hat crew is pushing Wayland so hard to prevent people from using 30 years' worth of lightweight X window managers that exist and are better than GNOME.
Essentially, what could depend on shared standards and implementations in X11, can't do so in Wayland, and there are two major forks when it comes to protocol extensions, as well as major fork between GNOME and everyone else on topic of Server-Side decorations.