This latest video of Wayland from @BrodieOnLinux is one of the most elitist and bad faith video I saw of him when trying to defend wayland.
Here's a few points.
* This is pedantic and in a bad faith too but if all minorities(this includes disabled people too) are equal, 1% affected shouldn't be considered second class citizen because "nah, it's only 0.1% of people will need this feature". If minority matters, this is something that should never be used as an argument.
* On the 1% of userbase not being "important". Dude, Linux is that "1%", before Valve investing a lot on Linux, it wasn't even 1% on steam charts and even today it didn't go above 3%. By your logic Valve should never invested on it.
* As someone who had to work/learned about accessibility it's something that it's a complex can of worms but the issue isn't that on windows or Mac isn't good out of the box.
The issue is that while windows/Mac/x11 provides API's or ways to deal with that, wayland doesn't and that's the problem. You can make a good/use good accessibility software but you CAN'T on wayland without going full root mode.
@kumicota@BrodieOnLinux >The issue is that while windows/Mac/x11 provides API's or ways to deal with that, wayland doesn't and that's the problem. You can make a good/use good accessibility software but you CAN'T on wayland without going full root mode.
I didn't even think about accessibility software. That's a good point. You also can't use push-to-talk in a background application like Discord or Mumble nor can you use OBS keyboard shortcuts which makes Wayland suck for gaming. Yeah performance is better but now you can't talk to your teammates without hotmicing. Wayland likely won't see much adoption for gaming until that's address. Oh yeah plus nvidia.
GPUs are also doing similar things with monitors now (freesync, gsync) because the display out knows more about the frame being done than the link does.
this is one of those things that just makes you want to drive a killdozer in to freedesktop. it's not a hill that was worth dying on.
Wayland definitely falls in the category of “I don’t know why people put this gate here, so let’s get rid of it…” They’re only now running head long into why the “gate was there” as they “rediscover” why for themselves. Requirements and design phase failures are the worst.
It's a bit complicated but the main gist of it is that they want to sandbox every app. Like how the app can't control its positioning, it can't inject/listen to keypresses(used in voicechat(TTS), obs,...), change the z-level and more. So a lot of things that just works everywhere doesn't but the problem is that wayland devs don't wanna change that, for example, screenshot apps don't work on it because it can only screenshot itself.
While x11 is a security mess, wayland tried to fix that in the worst way possible, by making everything to not work
I really have no fucking idea about the technicals when it comes to Wayland vs X11, but I do have a little bit of experience now as a user. I've resolved numerous issues instantly (and usually these are issues around running games with wine) by just switching back to X.
I have had good results with Pipewire, especially with respect for easy audio routing, and it's nice not to have to start up jackd just to get that done, but I can't say Wayland has really helped me out yet in a practical way.