Comment by WhyNotHugo

Wayland doesn't have broken technical decisions, they're just different and require applications to adapt.

A typical examples is global hotkeys. On X11, any application can monitor all keystrokes at any time. On Wayland, applications only get keyboard events if they're in foreground. Global hotkeys must be done via a separate compositor API. This breaks applications which expect to be able to detect keystrokes when they're in background, but the "feature" they relied on also allows any random application to include a keylogger. Such applications need to update.

You mention Firefox uses XWayland. Firefox also has native Wayland support (I'm writing on it right now!). This is likely a mis-configuration at some level, or maybe the Firefox version is too old.

OTOH, things like scaling are completely broken on X11, and while the hacks around it improve over the years using a HiDPI display will likely never be as smooth as on Wayland. And if you have a laptop with a HiDPI display and a LowDPI external monitor, one of them is going to suck forever on Xorg.

We are, of course, on a transitional period. A lot of applications still need refinement. Qt in particular still has lots of bugs on Wayland. But these can be fixed, there's no broken design decision which makes them unfixable.