| ▲ | graemep a day ago | |||||||||||||||||||||||||
I still run into problems with Wayland because not everything works well with Wayland. here is a recent example that other people have already run into: https://forums.wesnoth.org/viewtopic.php?p=706242#p706242 I also had Wayland refuse to run at all on an ARM device and this seems to be common too. I had to switch to X11 until the bug was fixed. | ||||||||||||||||||||||||||
| ▲ | remix2000 20 hours ago | parent [-] | |||||||||||||||||||||||||
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. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||