Too bad Linux completely abandoned accessibility with Wayland by putting accessibility API implementations up to the distros. Which, by far, don’t. And when they do it’s fragmented as fuck.
Making Linux an absolute no go for anyone that needs accessibility tools like Talon, which does work on X11 APIs. Since those were actually consistent.
Wayland is responsible for kneecapping linux desktop in so many ways its infuriating, especially since linux basically figured out the golden standard of UX design back in the 2000s with stuff like GNOME 2 and Compiz.
It’s such an unnecessary burden with progress as slow as ripoff projects like star citizen.
I hope valve picks up the slack with frog protocols or at least gets PRs merged, because it would be stupid to ship steam machine and then explain to the user that the clipboard doesn’t work yet, even though it used to work perfectly fine in X11.
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.
I really do not like such comments. Do free alternatives always have to be better than everything else? Even if people would find out that Facebook was always watching them via their cameras and were selling their nude pictures to the Hezbollah, someone will jump into the comments and say that they can’t use Mastodon, because some bogus reason. Yeah, accessibility could be better, but have you even taken a look at whatever nightmare UIs Microsoft has been pushing for years?
Too bad Linux completely abandoned accessibility with Wayland by putting accessibility API implementations up to the distros. Which, by far, don’t. And when they do it’s fragmented as fuck.
Making Linux an absolute no go for anyone that needs accessibility tools like Talon, which does work on X11 APIs. Since those were actually consistent.
Wayland is responsible for kneecapping linux desktop in so many ways its infuriating, especially since linux basically figured out the golden standard of UX design back in the 2000s with stuff like GNOME 2 and Compiz.
It’s such an unnecessary burden with progress as slow as ripoff projects like star citizen.
I hope valve picks up the slack with frog protocols or at least gets PRs merged, because it would be stupid to ship steam machine and then explain to the user that the clipboard doesn’t work yet, even though it used to work perfectly fine in X11.
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.
I really do not like such comments. Do free alternatives always have to be better than everything else? Even if people would find out that Facebook was always watching them via their cameras and were selling their nude pictures to the Hezbollah, someone will jump into the comments and say that they can’t use Mastodon, because some bogus reason. Yeah, accessibility could be better, but have you even taken a look at whatever nightmare UIs Microsoft has been pushing for years?