
This is comparing different DE’s how is this at all useful? They could literally compare kde in Wayland and x11 directly (at least until 6.8) and yet didn’t? This is more comparing different implementations in an apples to oranges comparison than Wayland and x11 implementations in an apples to apples comparison.
Only ran once, doesn’t measure x server cpu usage, claims “not necessarily more efficient” despite kwin and labwc showing higher framerate for seemingly similar power usage numbers, no discussion of e.g. frame times, consistency and cpu vs gpu limited…
For dual monitors and partial scaling wayland have been a bless.
It’s not that’s more or less efficient or more of less fast. It’s that’s been able to do things thar X was unable to and had to be practically hacked to get a clunky solution.
Like what?
Partial scaling.
X way to do it was a hack that works not so well.
Didn’t because Wayland can produced more performance and that’s why it’s using more power?
I’ve been running nothing than sway after doing a quick test on my rpi 4, running doom 3 – and the performance difference was really significant.
I’d be interested in tests across hardware of different ages (but as others have said, same/similar DEs/WMs/compositors as much as possible, please). While I have no proof, I’d guess that Wayland is making assumptions that would make it less efficient on some older kit.
Last time I tried wayland (with sway), Krita didn’t support it natively, and tho you could run it with xwayland, there was an insufferable cursor offset bug that I couldn’t get rid of safe by returning to X11 (with i3). Supposedly, Krita now supports wayland so I figured I might try again… But when I got the error in sway saying it didn’t support proprietary nvidia drivers, I figured I just… Wouldn’t do that. Yeah, maybe it’d work just switching to nouveau drivers, but I’ve wrestled with nvidia drivers and haven’t had a problem about it for a while, I don’t want to shake that wasp’s nest again. And I don’t know how many other parts of my config I’m gonna have to change as well, and I don’t feel like doing that now. At this point I don’t have any reason not to switch to wayland, but I also don’t really have much reason to switch, and being marginally faster isn’t enough for me.
This is stupid and probably ignorant too, but I couldn’t get RDP dynamic window resizing to work on Wayland no matter what I tried and went back to gnome which works great.
Gnome isn’t orthogonal to Wayland.
You’d need to check if you were using the X11 or Wayland session of Gnome
Ok… ? Then it was X11 that worked not Wayland… ffs
Gnome has defaulted to Wayland for a long time, so it sounded more like you had an issue with a different desktop environment, not X11 vs Wayland




