(no title)
criticalfault | 2 months ago
The only thing maybe worth discussing is video acceleration. this aside, I have been using gnome on Wayland for years and no problems what-so-ever. I really don't know what the fuss is about.
I would prefer that people start moving this legacy nonsense behind and finally start accepting new and better things and focusing on things that have future. Same thing happened with systemd, it improves massively everything Linux, yet some people just want their services started with scripts.
What problems do you have when things don't work for you on Wayland?
yjftsjthsd-h|2 months ago
* straight up doesn't work on at least one of my laptops (driver problems AFAICT)
* does run on the other one, but crashes at an alarming rate compared to Xorg
* breaks all of my accessibility tools (some have (worse) replacements, some don't)
criticalfault|2 months ago
here is my state of laptops:
* Dell latitude with old Intel 8gen CPU, it works fine (Linux kernel causes problems with PSR, but this has nothing to do with Wayland and disabling it fixes the problem, same thing with cstates)
* Dell latitude with 10gen CPU, works fine.
* Huawei d15 with Ryzen 3000 Apu, works fine.
ok. for accessibility it's fair enough as a critique. I don't use it so can't say. As far as I can tell this hasn't been in focus at all. but most of this is on the toolkit side, not Wayland (even though here one thing is mentioned as Wayland specific, just briefly went through the post)
https://blogs.gnome.org/a11y/2024/06/18/update-on-newton-the...
oblio|2 months ago
You can blame the apps all you want, but it's a fact of life, and Wayland has been around for 18 years.
At this point you'd hope they'd pull an early 90s Microsoft: https://www.joelonsoftware.com/2000/05/24/strategy-letter-ii...
IshKebab|2 months ago
I think we are finally at the point where you can say most things work and it's silly to go back to X11, but even so Wayland has clearly been a huge failure.