I say that despite the fact that I think wayland was a poorly conceived, designed, implemented, and marketed project that has set back the adoption of the linux desktop by years.
https://news.ycombinator.com/item?id=46085593 ("KDE going all-in on a Wayland future (kde.org)"—46 comments)
Why?
And that having fucktons of incompatible compositors because wayland, by design, does not want to standardize things they decided would be harmful to myself if I needed them is also a good path forward.
Meanwhile the very real problem of "developers can't write an application that targets wayland, is brushed under the carpet, and then the entire house it's in is also buried in sand. Devs can target gnome, kde or whatever. But they'd have to support them separately. And there are certain devs who explicitly say they will not be implementing wayland support because of these issues. But at least we have solved XEyes's security issues!
Last time I started a wayland plasma session it kept resetting my screen brightness to 100% every time they woke from sleep. The time before that I crashed the entire desktop, dropping me back to the terminal, when I tried to drag a hyperlink between windows.
Those might have been fixed and I might try wayland again next time I update and reboot.
I don't care about its supposed advantages.
Wayland reminds me very much of the Disk Utility application that shipped with Mac OS X El Capitan. The developers rewrote it because the original person who wrote it wasn't at Apple anymore and it ended up being pretty much useless due to massive amount of missing features.
>I don't care about its supposed advantages
Since it will be the only game in town soon, it's time to start caring - or people will also have to change DEs and other apps, which would be much more trouble than getting on with the program.
thankfully this hasn't been a problem so far, hopefully the end of x11 is still about 20 years away, like fusion.
What does that mean?
They could promise to drop support for it once the wayland one reaches feature parity. If any "significant issues" remain, then it's simply not ready for release.
I hate this modern trend of releasing stuff before it is done. And in the commercial space we are now moving on to releasing stuff before they even get started on development. Selling promises. "Buy our shit now and we promise that next year it will be able to do X!"
Also 6.8 is at least 2 years out, so there's still time to work the remaining issues out. As far as I know only speech input remains a major problem, so hopefully they'll figure that out.
> Also 6.8 is at least 2 years out
It's been decades since Wayland was "ready". But surely two more years...
The bright, complete, unfettered future always just a few more versions and a few more years over the horizon.
Decades? Really?
Wayland very first release was 17 years ago in 2008 and QT didn't support it until 2015. xdg-desktop-portal first stable release was in 2018 and PipeWire in 2023.
I thought we had peaked with systemd when it came to FUD here but Wayland might give it a run for its money.
But you do not get to demand that future versions are only ever implemented your way. If that's what you want, fork the project or pay someone to do it for you. Acting entitled about the work of volunteers who are sharing it with you for free is not a good look.
What accessibility features will you be missing in KDE Plasma 6.8?
I like KDE but I'm still running X11 on Void Linux, partly because I just don't feel like trying to switch over to Wayland and reconfigure my two systems.