Screen sharing is a pain, I did get it working on Arch finally though, but it's still a pain at this point. And I only got "screen" sharing i.e. not "app sharing" or "monitor/virtual-monitor sharing" working. Latter part could well be some more config or tweaking I need to do, regardless it's not the users fault if they can't figure this out in Wayland when it works fine everywhere else out of the box. I've gotten it to work well enough for my personal use case but it's definitely not far enough along for the typical use case.
X11 isn't that great with monitor setups with multiple DPI. It's certainly one of the biggest user facing "wins" for Wayland but much like you dismiss playing WoW as something you don't do most users don't deal with mixed DPI setups so the biggest "win" really doesn't mean much to most. That doesn't mean it can't be a great reason for you to prefer Wayland though.
Sway won't even launch on my Nvidia computers so I've just got them running Windows with WSL. I don't think it's X11/Wayland's fault on this one, Nvidia is just a bit too locked down when it comes to Linux preventing good support from anybody. At the same time the professional hardware is just better so you don't always have a choice to just use an AMD card even if you were willing to change hardware for better support.
I really like my Wayland setup but it's important to understand the tradeoffs I was willing to make and the efforts I was willing to put in don't mean Wayland was perfect it means it was better for my situation. For another user it's probably a HORRIBLE fit right now. That's not their fault, nor anyone else's fault, it's just a difference in use case.
I think Wayland is getting pretty close (particularly for the less stubborn willing to let xwayland run as well) to being ready for most users but that's what many have been trumpeting for 5 years so it's created a bit of pushback when you say it is now.
To be honest, it was not a complete dismissal on being able to run wow under wine.
In my opinion neither x11 or wayland is perfect both brings huge amount of pain. Whereas wayland brings the least amount of pain for my usecase and shows the only prospect of improvement.
If I were a sensible person I would just use windows with wsl where’s absolutely everything just works as intended and there’s no tugwar. But I’m too stubborn for that and I hope I will one day install Linux and everything just works without having to do a extensive research for compatibility and workarounds
Screen sharing is a pain, I did get it working on Arch finally though, but it's still a pain at this point. And I only got "screen" sharing i.e. not "app sharing" or "monitor/virtual-monitor sharing" working. Latter part could well be some more config or tweaking I need to do, regardless it's not the users fault if they can't figure this out in Wayland when it works fine everywhere else out of the box. I've gotten it to work well enough for my personal use case but it's definitely not far enough along for the typical use case.
X11 isn't that great with monitor setups with multiple DPI. It's certainly one of the biggest user facing "wins" for Wayland but much like you dismiss playing WoW as something you don't do most users don't deal with mixed DPI setups so the biggest "win" really doesn't mean much to most. That doesn't mean it can't be a great reason for you to prefer Wayland though.
Sway won't even launch on my Nvidia computers so I've just got them running Windows with WSL. I don't think it's X11/Wayland's fault on this one, Nvidia is just a bit too locked down when it comes to Linux preventing good support from anybody. At the same time the professional hardware is just better so you don't always have a choice to just use an AMD card even if you were willing to change hardware for better support.
I really like my Wayland setup but it's important to understand the tradeoffs I was willing to make and the efforts I was willing to put in don't mean Wayland was perfect it means it was better for my situation. For another user it's probably a HORRIBLE fit right now. That's not their fault, nor anyone else's fault, it's just a difference in use case.
I think Wayland is getting pretty close (particularly for the less stubborn willing to let xwayland run as well) to being ready for most users but that's what many have been trumpeting for 5 years so it's created a bit of pushback when you say it is now.