Most people won't care, but for a number of us Wayland is stubbornly refusing to support functionality we see as dealbreakers.
I believe the main holdup is a desire for Wayland to be usable with e.g. VR interfaces where there is no simple 2d grid.
Out of curiosity, how do you want the file manager to behave? And did you write your own or are you using an existing one that works that way?
Though in this context it just seems to be the number of people working on the code on a consistent basis.
Really the only high-profile 'switch' in recent times I can think of is that Fedora promoted KDE to be first-class ('edition') alongside Gnome, instead of delegated to a more second-class spin. And while KDE is a bit more conservative in this regard, I believe that in the long term KDE also wants to go Wayland-only at some point.
Personally I did switch from Gnome to KDE some time after Gnome 40, since I quite liked 3.x but the UI overhaul 40 did wasn't really my thing. It also helps that KDE got a lot better in recent years.
True.
But does not address the fact that Wayland is a bad solution to X11's problems, and that its architecturally broken from inception.
Most of the issues and slow adoption were because the core protocol was deliberately kept extremely minimal, and agreeing on all the needed extensions took a long time. Don't take it from me, but rather from KDE developer Nate Graham: https://pointieststick.com/2023/09/17/so-lets-talk-about-thi...
As such, anyone who tried it early probably had to deal with a pretty large amount of non-working stuff, but by now the platform is capable of most features people require and the biggest remaining bottleneck is that software needs to use these new APIs.
For example, terminal transparency using Konsole on KDE flickers for me.
Its nearly there, but not quite. Maybe Gnome has no such issues?