luna the doggie :neofox_snug: :therian:@lunareclipse@snug.moe
The thing to realize about Wayland is that noone is out to get you.
Most of the problems people have a knee jerk reaction about were either fixed in the past few years or are being actively worked on. Sometimes it takes a long time because people want to actually do it properly and not just do a quick hack, and that can involve some experimentation and failures before a good solution is settled on. Also creating standards that all major DEs and UI toolkits will agree on can be a challenge.
X11 was made in a time where you ran your software on a mainframe but ran the GUI on a separate computer, noone thought about security yet and hardware accelerated rendering wasn't a concern.
At this point it's a massive clusterfuck full of hacks that noone wants to maintain.
This is why Wayland exists, because people actually want to work on it, and they want to use the experience from the past to make something that works much better in the modern world, where your GUI apps run directly on your computer, want hardware acceleration, and you may want them to be sandboxed for security reasons.
There is XWayland for compatibility, with implementations ranging from being built into the compositor (KWin) to being a layer on top (xwayland-satellite).
I know at least one maintainer of a Wayland compositor that specifically only supports the latter approach because they don't want to deal with implementing any cursed X11 logic.