one of the main reasons the linux kernel is where it is today: “never break userspace”
unfortunately not every project keeps to this principle.
There are good reasons to break userspace sometimes. If we would never do so, we would stuck on X11 forever.
Wayland is definitely on the side of not breaking userspace, though. The API design, xWayland compatibility layer, and recent focus on protocols to fix missing functionality from xorg are all designed to make Wayland a seamless transition.
Otherwise we’d have been using Wayland as the only option for years now.
“never break userspace”
As Linus once, very articulately, reminded that one guy.
To have this laundry list of negatives get a reply basically saying “yeah, it’s bad, but we need to impress the stakeholders by forcing a Wayland default even if it doesn’t work correctly” is baffling.
I use SDL so this hits a bit closer to home. Hopefully they can arrive at a conclusion that isn’t harmful to us devs. It’s already kind of a tossup whether it’s even worth it to provide a native Linux build when Proton works so well anyway. I can’t imagine this will help.
Gnome has been running user space applications just fine for me on Wayland, Arch Linux.
There were some issues about 2 years ago. I have no complaints for last 12 months.
Wayland is today’s life for some.
- Steam gaming , proton and native
- visual studio code
- qemu running windows
- app interrupting work to relax eyes
- old mysql dashboard ui
Basically, I have not seen app specific issues for my user flow.
Wayland is a painful future, it is just a fact.
That’s fine, we don’t need to rush things
