Wayland has a bright future ahead: The move from Xorg to Wayland had a rough start, but things have improved, and there is an exciting roadmap for the future.
-
Things like desktop automation, screen sharing, screen recording, remote desktop etc. are incredibly broken, with no hope in sight because the core design of Wayland simply didn't account for them(!?), apparently.
Add to that the decision to push everything downstream into compositors, which led to widespread feature fragmentation and duplicated effort.
Add to that antagonizing the largest graphics chipset manufacturer (by usage among Linux desktop users) for no good reason. Nvidia has never had an incentive to cater to the Linux desktop, so Linux desktop users sending them bad vibes is... neither here nor there. It certainly won't make them move faster.
Add to that the million little bugs that crop up when you try to use Wayland with any of the desktop apps whose developers aren't snorting the Koolaid and not dedicating oustanding effort to catching up to Wayland – which is most of them.
people dont like change
I cannot use Wayland.
I'm an average Linux desktop user, who has an Nvidia card, has no need for Wayland "security", doesn't have multiple monitors with different refresh rates, uses desktop automation, screen sharing, screen recording, remote desktop on a daily basis, and uses lots of apps which don't work perfectly with Wayland.
...how and why would I subject myself to it? I'd have to be a masochist.
Things like desktop automation, screen sharing, screen recording, remote desktop etc. are incredibly broken, with no hope in sight because the core design of Wayland simply didn't account for them(!?), apparently.
All of those things function on Wayland using the right protocols. If they dont work for you, the app your using has chosen not to implement Wayland support yet.
For automation there is ydotool and wlrctl. Ive also seen a tool called Hawck which seems neat, but I haven't tried it.
I've never seen an issue with screen recording, OBS has worked fine with Wayland for a long time. I use GPU Screen Recorder on Wayland everyday.
Screensharing portals have existed for a while now, I haven't run into any apps that still haven't implemented them. Ive used it just fine on Discord and through multiple browsers.
Remote desktop also has a portal that any remote desktop app could implement. Rustdesk has experimental Wayland support which has worked for me. GNOME and Plasma also have built in RDP.
-
Need X-kill replacement.
Plasma and Hyprland already have one
-
god i wish. half of my X11 apps don't work, some that used to keep breaking without reason.
Steam works through the XWayland compatibility layer
unless you use an environment that doesn't support XWayland, like niri. xwayland-sattelite used to be the easier route in that case but that seems to be broken now.
What issues do half of your X11 apps? Ive never had an issue with an X11 app running through Xwayland, although I also dont have many X11 apps left.
-
Sorry, Ctrl + Win (or relevant OS button) + Esc, but yeah it's been pretty useful in a pinch
You can use Meta or Super for a more agnostic keycode
-
I’ll bite. It’s getting better, but still a long way to go.
- No commercially viable remote desktop or thin client solutions. I’m not talking about just VNC, take a look at for example ThinLinc to see what I’m looking for - a complete solution. (Also, it took like ten rough years before basic unencrypted single user VNC was available at all.) Free multimillion dollar business idea right here folks!
- Related to the above point - software rendered wayland is painful. To experience this yourselves, install any distro in VirtualBox or VMWare or whatever and compare the usability between a Xorg DE (with compositing turned off) and the same Wayland DE. Just look at the click-to-photon latency and weep. I’ve seen X11 perform better with VNC over WAN.
- ”We don’t need network transparency, VNC will save us”. See points above.
- ”Every frame is perfect” went just as well as can be expected, there is a reason VSYNC is an option in games and professional graphics applications. Thanks Valve.
- I’m assuming wlroots still won’t work on Nvidia, and that the Gnome/KDE implementations are still a hodgepodge, and that Nvidia will still ask me to install the supported Xorg drivers. If I’m wrong, it only took a decade or so to get a desktop working on hardware from the dominant GPU vendor. (Tangentially related - historically the only vendor with product lines specifically for serving GPU-accelerated desktops to thin clients)
- After over a decade of struggles, we can finally (mostly) share out screens in Zoom. Or so I’m told.
But what do I know, I’ve only deployed and managed desktop linux for a few thousand people. People were screaming about these design flaws back in 2008 when this all started. The criticisms above were known and dismissed as FUD, and here we are. A few architectural changes back then, and we could have done this migration a decade faster. Just imagine, screen sharing during the pandemic!
As an example, see Arcan, a small research project with an impressively large subset of features from both X11 and Wayland (including working screen sharing, network transparency and a functioning security model). I wouldn’t use it in production, but if it was more than one guy in a basement working on it, it would probably be very usable fairly fast, compared to the decade and half that RedHat and friends have poured into Wayland thus far. Using a good architecture from the start would have done wonders. And Wayland isn’t even close to a good architecture. It’s just what we have to work with now.
Hopefully Xorg can die at some point, a decade or so from now. I’m just glad I don’t work with desktops anymore, the swap to Wayland will be painful for a lot of organisations.
Rustdesk is an alright remote desktop option, although it definitely far from perfect. Wayland offers the support remote desktop needs, this is just up to someone wanting a solution enough to make it.
I agree that the "every frame being perfect" thing was dumb, but tearing support exists so its not really a complaint anymore.
Nvidia does work fine on every major Wayland implementation.
Screensharing works fine.
I understand the disappointment in how long Wayland is taking to be a perfect replacement to X11, but a proper replacement should absolutely not be rushed. X11 released 40 years ago, 15 years to make a replacement with better security and more features is fine.
Wayland has put a huge emphasis on improved security, which is also one of the biggest reasons some features have taken so long. This is a good thing, rushing insecure implementations of features is a horrible idea for modern software that will hopefully last a long time.
In its current state, Wayland is already good for the large majority of use cases.
-
This post did not contain any content.
At leasr it just works with tailsOS
-
Things like desktop automation, screen sharing, screen recording, remote desktop etc. are incredibly broken, with no hope in sight because the core design of Wayland simply didn't account for them(!?), apparently.
Add to that the decision to push everything downstream into compositors, which led to widespread feature fragmentation and duplicated effort.
Add to that antagonizing the largest graphics chipset manufacturer (by usage among Linux desktop users) for no good reason. Nvidia has never had an incentive to cater to the Linux desktop, so Linux desktop users sending them bad vibes is... neither here nor there. It certainly won't make them move faster.
Add to that the million little bugs that crop up when you try to use Wayland with any of the desktop apps whose developers aren't snorting the Koolaid and not dedicating oustanding effort to catching up to Wayland – which is most of them.
people dont like change
I cannot use Wayland.
I'm an average Linux desktop user, who has an Nvidia card, has no need for Wayland "security", doesn't have multiple monitors with different refresh rates, uses desktop automation, screen sharing, screen recording, remote desktop on a daily basis, and uses lots of apps which don't work perfectly with Wayland.
...how and why would I subject myself to it? I'd have to be a masochist.
screen sharing, screen recording, remote desktop
ive used all three on wayland without issues.
-
I’ll bite. It’s getting better, but still a long way to go.
- No commercially viable remote desktop or thin client solutions. I’m not talking about just VNC, take a look at for example ThinLinc to see what I’m looking for - a complete solution. (Also, it took like ten rough years before basic unencrypted single user VNC was available at all.) Free multimillion dollar business idea right here folks!
- Related to the above point - software rendered wayland is painful. To experience this yourselves, install any distro in VirtualBox or VMWare or whatever and compare the usability between a Xorg DE (with compositing turned off) and the same Wayland DE. Just look at the click-to-photon latency and weep. I’ve seen X11 perform better with VNC over WAN.
- ”We don’t need network transparency, VNC will save us”. See points above.
- ”Every frame is perfect” went just as well as can be expected, there is a reason VSYNC is an option in games and professional graphics applications. Thanks Valve.
- I’m assuming wlroots still won’t work on Nvidia, and that the Gnome/KDE implementations are still a hodgepodge, and that Nvidia will still ask me to install the supported Xorg drivers. If I’m wrong, it only took a decade or so to get a desktop working on hardware from the dominant GPU vendor. (Tangentially related - historically the only vendor with product lines specifically for serving GPU-accelerated desktops to thin clients)
- After over a decade of struggles, we can finally (mostly) share out screens in Zoom. Or so I’m told.
But what do I know, I’ve only deployed and managed desktop linux for a few thousand people. People were screaming about these design flaws back in 2008 when this all started. The criticisms above were known and dismissed as FUD, and here we are. A few architectural changes back then, and we could have done this migration a decade faster. Just imagine, screen sharing during the pandemic!
As an example, see Arcan, a small research project with an impressively large subset of features from both X11 and Wayland (including working screen sharing, network transparency and a functioning security model). I wouldn’t use it in production, but if it was more than one guy in a basement working on it, it would probably be very usable fairly fast, compared to the decade and half that RedHat and friends have poured into Wayland thus far. Using a good architecture from the start would have done wonders. And Wayland isn’t even close to a good architecture. It’s just what we have to work with now.
Hopefully Xorg can die at some point, a decade or so from now. I’m just glad I don’t work with desktops anymore, the swap to Wayland will be painful for a lot of organisations.
Your point is that it is still rough and then you bring up a bunch of stuff that is no longer an issue.
NVIDIA in particular is basically a solved problem with both explicit sync and open source kernel modules as the default from NVIDIA themselves.
Rustdesk and Waypipe are probably going to eat into your billion dollars (and network transparency laments).
As stated in the article, opt-out vsync is already a thing (though not widely implemented yet).
I have not used GNOME in a while but KDE on Wayland is great. And the roadmap certainly looks a lot nicer than xorg’s.
I was on a video call in Wayland an hour ago. I shared my screen.
If that is your full list, I think you just made the case that Wayland is in good shape.
-
You can use Meta or Super for a more agnostic keycode
I thought "Meta" was AltGr and Super is the "windows key".
-
Things like desktop automation, screen sharing, screen recording, remote desktop etc. are incredibly broken, with no hope in sight because the core design of Wayland simply didn't account for them(!?), apparently.
Add to that the decision to push everything downstream into compositors, which led to widespread feature fragmentation and duplicated effort.
Add to that antagonizing the largest graphics chipset manufacturer (by usage among Linux desktop users) for no good reason. Nvidia has never had an incentive to cater to the Linux desktop, so Linux desktop users sending them bad vibes is... neither here nor there. It certainly won't make them move faster.
Add to that the million little bugs that crop up when you try to use Wayland with any of the desktop apps whose developers aren't snorting the Koolaid and not dedicating oustanding effort to catching up to Wayland – which is most of them.
people dont like change
I cannot use Wayland.
I'm an average Linux desktop user, who has an Nvidia card, has no need for Wayland "security", doesn't have multiple monitors with different refresh rates, uses desktop automation, screen sharing, screen recording, remote desktop on a daily basis, and uses lots of apps which don't work perfectly with Wayland.
...how and why would I subject myself to it? I'd have to be a masochist.
Are you a Debian Stable user perhaps? It feels like you have been trapped on an island alone and are not aware that WWII is over.
-
Now consider that most enterprises are about five years behind that. Takes a few years before what’s available in Fedora trickles down to RHEL, and a few more years before it’s rolled out to clients. Ubuntu is on a similar timeline.
The fixes you got two years ago might be rolled out in 3 years in these places. Oh, and these are the people forking up much of the money for the Wayland development efforts. The current state of Wayland if you pay for it is kinda meh.
RHEL 9 defaulted to Wayland in 2022. RHEL 10 will not even include Xorg.
I agree that businesses lag, often by years. So the fact that RHEL is so far along in the Wayland transition kind of shows how out-of-date the anti-Wayland rhetoric is.
-
This post did not contain any content.
"rough start" is putting it mildly. 🤭
-
Your point is that it is still rough and then you bring up a bunch of stuff that is no longer an issue.
NVIDIA in particular is basically a solved problem with both explicit sync and open source kernel modules as the default from NVIDIA themselves.
Rustdesk and Waypipe are probably going to eat into your billion dollars (and network transparency laments).
As stated in the article, opt-out vsync is already a thing (though not widely implemented yet).
I have not used GNOME in a while but KDE on Wayland is great. And the roadmap certainly looks a lot nicer than xorg’s.
I was on a video call in Wayland an hour ago. I shared my screen.
If that is your full list, I think you just made the case that Wayland is in good shape.
Yeah, the few thousand users I managed desktops for will remain on X for the next few years last I heard from my old colleagues.
Because of my points above
But good that your laptop works now and that I can help my grandma over teamviewer again.
-
This post did not contain any content.
As an average desktop user, I've run into very little pushback on Wayland. Its made huge leaps in a short amount of time.
-
RHEL 9 defaulted to Wayland in 2022. RHEL 10 will not even include Xorg.
I agree that businesses lag, often by years. So the fact that RHEL is so far along in the Wayland transition kind of shows how out-of-date the anti-Wayland rhetoric is.
Exactly my point. The issues people consider ”solved” with wayland today will be solved in production in 3-5 years.
People are still running RHEL 7, and Wayland in RHEL 9 isn’t that polished. In 4-5 years when RHEL 10 lands, it might start to be usable. Oh right, then we need another few years for vendors to port garbage software that’s absolutely mission critical and barely works on Xorg, sure as fuck won’t work in xwayland. I’m betting several large RHEL-clients will either remain on RHEL8 far past EOL or just switch to alternative distros.
Basically, Xorg might be dead, but in some (paying commercial) contexts, Wayland won’t be a viable option within the next 5-10 years.
-
Rustdesk is an alright remote desktop option, although it definitely far from perfect. Wayland offers the support remote desktop needs, this is just up to someone wanting a solution enough to make it.
I agree that the "every frame being perfect" thing was dumb, but tearing support exists so its not really a complaint anymore.
Nvidia does work fine on every major Wayland implementation.
Screensharing works fine.
I understand the disappointment in how long Wayland is taking to be a perfect replacement to X11, but a proper replacement should absolutely not be rushed. X11 released 40 years ago, 15 years to make a replacement with better security and more features is fine.
Wayland has put a huge emphasis on improved security, which is also one of the biggest reasons some features have taken so long. This is a good thing, rushing insecure implementations of features is a horrible idea for modern software that will hopefully last a long time.
In its current state, Wayland is already good for the large majority of use cases.
What I’ve seen of rustdesk so far is that it’s absolutely not even close to the options available for X. It replaces TeamViewer, not thin clients.
You would need the following to get viability in my eyes:
- Multiple users per server (~50 users)
- Enterprise SSO authentication, working kerberos on desktop
- Good and easily deployable native clients for Windows, Linux and Mac, plus html5 client
- Performant headless software rendered desktops
- GPU acceleration possible but not required
- Clustering, HA control plane, load balancing
- Configuration management available
This isn’t even an edge case. Current and upcoming regulations on information security drags the entire industry this way. Medical, research, defence, banking, basically every regulated landscape gets easier to work in when going down this route. Close to zero worries about endpoint security. Microsoft is working hard on this. It’s easy to do with X. And the best thing on Wayland is RustDesk? As stated earlier, these issues were brought up and discarded as FUD in 2008, and here we are.
Wayland isn’t a better replacement, after 15 years it’s still not a replacement. The Wayland implementations certainly haven’t been rushed, but the architecture was. At this point, fucking Arcan will be viable before Wayland.
-
This post did not contain any content.
The gnome implementation that I'm forced to use is god damn awful. This whole eventbus implementation is so bad, it misses events and doesn't always register key-up, when I'm switching workspaces. I do it a lot, and the key gets stuck spamming the same letter, because it didn't register key up!! Hell sometimes it doesn't register keydown, super annoying when writing passwords.
Random crashes of gnome happens more often than I would like to admit, and all that you've been working on is gone aswell. What a garbage design, why the fuck should the wm own the processes, I swear the wayland people live on a another planet.
And the whole permissions thing to ensure privacy, mf this is linux, stop making me do workarounds for shit that you won't allow, because you haven't implemented the correct support for it.
I'm running Ubuntu 24.04, thing fucking sucks, I'm forced by work. Dude x11, just worked, like Wayland solved anything at all.
-
Whats rough?
Not sure if it was a kde issue or a wayland issue, but I tried it last year and had trouble with cursor locking.
Virtualbox had issues with the input being intermittent, and my mouse would move off the screen while gaming.
It might be fixed now, but I don't plan on trying it again for another few years, because what I'm using works for me.
-
The gnome implementation that I'm forced to use is god damn awful. This whole eventbus implementation is so bad, it misses events and doesn't always register key-up, when I'm switching workspaces. I do it a lot, and the key gets stuck spamming the same letter, because it didn't register key up!! Hell sometimes it doesn't register keydown, super annoying when writing passwords.
Random crashes of gnome happens more often than I would like to admit, and all that you've been working on is gone aswell. What a garbage design, why the fuck should the wm own the processes, I swear the wayland people live on a another planet.
And the whole permissions thing to ensure privacy, mf this is linux, stop making me do workarounds for shit that you won't allow, because you haven't implemented the correct support for it.
I'm running Ubuntu 24.04, thing fucking sucks, I'm forced by work. Dude x11, just worked, like Wayland solved anything at all.
X11 absolutely didn't just work, hence Wayland's entire existence and rapid adoption once it was mature enough to function. Xorg's decades old cobbles together code ase of awkward fixes for obscure issues and random contributions that had to be repeatedly fixed in every other patch is infamous as an example of how not to do FOSS software over time, and serves as a fatal warning to all open source projects.
Wayland has issues, and those issues are being fixed. Slow updating distros, as always, suffer the most with new software and paradigms. But whining about it hardly helps. This is foss land, contribute or report, never complain.
-
Exactly my point. The issues people consider ”solved” with wayland today will be solved in production in 3-5 years.
People are still running RHEL 7, and Wayland in RHEL 9 isn’t that polished. In 4-5 years when RHEL 10 lands, it might start to be usable. Oh right, then we need another few years for vendors to port garbage software that’s absolutely mission critical and barely works on Xorg, sure as fuck won’t work in xwayland. I’m betting several large RHEL-clients will either remain on RHEL8 far past EOL or just switch to alternative distros.
Basically, Xorg might be dead, but in some (paying commercial) contexts, Wayland won’t be a viable option within the next 5-10 years.
What you're describing aren't issues with Wayland.
Your complaints are that you're using old versions and poorly designed software.
Those aren't Wayland issues they're poor management and lack of investment
