Except accessibility, Wayland has been a huge upgrade over X11.
Much better security isolation, proper HDR, full multi-monitor support, full VRR support, better application scaling, no screen tearing and reduced latency. (The clipboard also works fine)
Without Wayland I would not be on Linux right now.
Their measurements are correct but not surprising, Wayland triple buffers everything on desktop. Currently triple buffering is only disabled in fullscreen applications, when the compositor supports it.
I wanted to take my own measurements with the newer tearing control protocol but didn’t get to it yet.
Almost nothing you mentioned here has to do with accessibility and accessibility tooling.
I get the feeling that most of the people replying here and downvoting the folks that are right don’t actually know what accessibility means.
Which… Honestly tracks. If the community in general doesn’t actually understand what accessibility is of course the projects themselves aren’t going to give a shit about accessibility.
And the Linux community, par for the course, shits on anyone who has real critical feedback.
Except accessibility, Wayland has been a huge upgrade over X11.
Much better security isolation, proper HDR, full multi-monitor support, full VRR support, better application scaling, no screen tearing and reduced latency. (The clipboard also works fine)
Without Wayland I would not be on Linux right now.
Latency actually is increased on Wayland: https://mort.coffee/home/wayland-input-latency/ and Dedoimedo’s Wayland articles.
Please correct me if I’m wrong and provide a source.
Their measurements are correct but not surprising, Wayland triple buffers everything on desktop. Currently triple buffering is only disabled in fullscreen applications, when the compositor supports it.
I wanted to take my own measurements with the newer tearing control protocol but didn’t get to it yet.
Almost nothing you mentioned here has to do with accessibility and accessibility tooling.
I get the feeling that most of the people replying here and downvoting the folks that are right don’t actually know what accessibility means.
Which… Honestly tracks. If the community in general doesn’t actually understand what accessibility is of course the projects themselves aren’t going to give a shit about accessibility.
And the Linux community, par for the course, shits on anyone who has real critical feedback.