Posted by hoechst 6 hours ago
Or maybe it just came out of nowhere and was never true.
I do know it is favoured by ricers with animations & transparency but I just use it to tile stuff. Think I selected it over sway & i3 due to wayland support at the time. Not sure.
Also, both the input latency (usb controller, and its driver), and screen latency (input latency + processing + update delay) are supposedly also affecting all measurements, but hopefully somewhat consistent or at least filtered out.
edit: no, this is the one I was remembering: https://farnoy.dev/posts/linux-latency
Wayland has been great for me for a few years now. I don't use Gnome or nvidia though.
You don't run GNOME on Wayland. You run GNOME's Wayland compositor, which is an entirely different implementation than Plasma's Wayland compositor.
I've not used gnome for years, but I have a vague memory of gnome/mutter running on a single main thread which used to lock up quite a lot (javascript etc). And because in X it was X that used to manage things like rendering the mouse pointer every frame, whereas in Wayland it flipped to mutter having to do it directly, the stalls were way more obvious in wayland than X, which is where I think a lot of this perception came from.
Again, not sure how much of this is accurate, but that's the point I was trying to make.
Wayland mouse movement lag is/can be/could/was in the order of several hundred milliseconds.
Its that that people notice, not 3 or 4ms difference in click response.