I don't see wayland ever being really usable. Wayland is now as old as Xorg was when wayland started because X11 is "old and crufty" and still not usable. And the "clean" protocol is simply lacking so again we started stacking whatever shit on top like compositor dependant extensions for screenshots or screensharing, desktop portals etc. and are STILL missing features like control over windows placement....
> Wayland is now as old as Xorg was when wayland started because X11 is "old and crufty" and still not usable.
How is this comparison supposed to make any sense? When Xorg started it was a fork of the existing XFree86 codebase (due to XFree86 changing license to one not deemed open source compatible), not starting from a clean sheet of paper. And XFree86 in turn wasn't a clean sheet implementation of the X protocols either, it IIRC started as a bunch of patches on top of the reference X11 codebase which goes back to the 1980'ies.
The big problem with Wayland I see is that every small app needs to do everything (fonts, ...) which can be a lot of startup overhead...
(I'm 100% not a fan of using a single process for all terminals).
tbf in reality nobody uses X11 corefonts anymore. Even on X11 all typical toolkits like GTK or Qt have been doing their own client side font rendering for years.
(but X11 still supports server side fonts if you want to make trivial clients)
I don't miss the font mismatch, partial Unicode, and the wrong mapping of ÅÄÖåäö of X11 servers...
There's so many irritations with using Wayland that I continue to strip it out of installs. Not being able to correctly use push-to-talk in voice chat apps because of window security is infuriating, and one app crashing still takes down the entire desktop.