Well that is a shame I guess, but I don’t tell anyone to switch to Wayland. I’m sure there are some cases where X windows work when Wayland doesn’t work at all and vice versa it’s also true. You’ll still be able to enjoy any Wayland-only apps in cage (or any other Wayland server with X backend), and I can use any X-only apps on Xwayland.

My point is that Wayland skips some overhead inherent to X, so it’s lighter on resources, and that enables some really fun things, like that tablet of mine being completely smooth rendering a 3d desktop with laughably small amount of ram and a really weak Intel SoC, but I won’t try to argue that one is always better than the other, because that’s not how things work.

And btw, I don’t know what Wayland has to do with ur cpu architecture, but I actually run a custom Wayland env on my armv7 Kindle (just for the lulz, that one) and that works as well as any armv7 thing.

It worked fine on my tablet since I got, and then broke. its now fixed and I am using it again. I had to use X for a few weeks and it does seem that Wayland is a lot less mature than X on ARM.

I do use Wayland on my desktop too, and the workaround in the case of Wesnoth was to use XWayland. One of the difficulties is that I have no idea whether the bug is in Wesnoth or KWin so do not know where to report it.