- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
This post is in part a response to an aspect of Nate’s post “Does Wayland really break everything?“, but also my reflection on discussing Wayland protocol additions, a unique pleasure that I have been involved with for the past months.
Before I start I want to make a few things clear: The Linux desktop will be moving to Wayland – this is a fact at this point (and has been for a while), sticking to X11 makes no sense for future projects.
By switching to Wayland compositors, we are already forcing a lot of porting work onto toolkit developers and application developers. This is annoying, but just work that has to be done. It becomes frustrating though if Wayland provides toolkits with absolutely no way to reach their goal in any reasonable way.
Many missing bits or altered behavior are just papercuts, but those add up. And if users will have a worse experience, this will translate to more support work, or people not wanting to use the software on the respective platform.
What’s missing?
- Window positioning
- Window position restoration
- Window icons
- Limited window abilities requiring specialized protocols
- Automated GUI testing / accessibility / automation
I spent probably way too much time looking into how to get applications cross-platform and running on Linux, often talking to vendors (FLOSS and proprietary) as well. Wayland limitations aren’t the biggest issue by far, but they do start to come come up now, especially in the scientific space with Ubuntu having switched to Wayland by default. For application authors there is often no way to address these issues.
To me, saying “wayland breaks things” is putting it backwards: at this point, it should be “[thing] still doesn’t work on wayland”.
Yeah.
If I installed, say, a messenger app on my phone that supports Android 4.0 but not Android 13, my reaction wouldn’t be “Android breaks this app!!”, my reaction would be “wow, this app hasn’t been updated to support any modern Android version, they need to fix that”
If Wayland was brand new and X11 was going to be killed in the very short term, then I’d agree, but that’s not the case. Wayland is over a decade old. Prominent distros have had it as the default since 2016. Shit, Debian has had it as the default since 2019. And that’s Debian.
I use an app to control the mouse and keyboard of my home theater PC from my smartphone. Will that ever be able to work?
Err… KDE Connect works for me. Have you tried it?
That PC is on Ubuntu LTS so it didn’t come to mind. The app I’ve been using is called Unified Remote and was generally pretty neat, not so much about tying my phone to the PC.
100% for the applications I use daily.
They did bring up a few specific scientific applications though that can’t be ported right now even though they would.