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.
-
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
-
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.
I've been using Wayland for years and I have no idea of what you are talking about (regarding the key-up, key-down issue, but I also haven't noticed any crash attributable to Wayland, specifically). Did the same computer you are using work with X11, and stopped working properly after an update? Could it be a hardware or driver issue? Also, has Canonical removed the X session from Ubuntu 24.04, or using Wayland is a company policy?
-
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.
Those are terribly run enterprises. I work for a giant multinational that is widely considered to be obsolete tech-wise ... I'm on fedora 42 on my work laptop. The team responsible for vetting, security and customising the deployment was ready day one.
Its 3-4 people catering for the ~2-3000 users that use the os internally.
I get the need for stability and repeatability in enterprise. I'm a sysadmin for more than 20 years.
That 3 year timeline could maybe move up a bit, even windows deployments are more or less up to date. Why would't linux be?Lastly, the more resistance to wayland, the longer it will take for it to reach a level of polish to where even you would aprove of.
When the switch became inevitable (distros defaulting, dropping x11), I installed it, lived with its crappy issues back then, reported said issues and moved on with my day.
-
This post did not contain any content.
Yeah it's at the point where i'm wondering if i still even need xorg. I'm still keeping it around just in case for now, but i could very easily purge it from my system anytime since i'm using nixos and all my xorg related settings are in a specific file. The main pet peeve i have with wayland is gaming related, and should hopefully improve when wine and proton go native wayland. I have a dual monitor setup and games always choose the wrong monitor by default, which means i can only use the resolution and refreshrate of the secondary monitor. I have a keybind to set the primary xwayland monitor with xrandr, which solves the problem, but it is a bit hacky. I also need to toggle vrr on and off with a keybind because it causes flickering on my monitor. It's a bit annoying but atleast it works, on xorg you can't even use vrr with multi monitor to begin with.
-
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.
Issue is already closed though and might have more to do with xwayland itself it seems. Also fwiw, i just tested steam on niri with xwayland-satellite a few weeks ago and it worked just fine.
-
This post did not contain any content.
I dunno why but I can't even log into KDE when I select wayland. The screen just turns black and unresponsive
-
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.
hard disagree about the permissions. If I want to run closed source programs like games, discord, zoom or whatever, I like knowing they can't log all my keys, take screenshots or even run their own version of windows recall without my explicit permission
-
I dunno why but I can't even log into KDE when I select wayland. The screen just turns black and unresponsive
Something similar happens to me on my desktop (debian 13) - it goes black then brings me back to the login screen. But in my case it's probably the nvidia drivers (proprietary). Not certain, though. Still happy on X11 for the meantime.
-
hard disagree about the permissions. If I want to run closed source programs like games, discord, zoom or whatever, I like knowing they can't log all my keys, take screenshots or even run their own version of windows recall without my explicit permission
yeah. the thing with the stuck keys and crashes is not normal. I've never experienced it (though I wanted to restart the window manager once), but also I'm using KDE
and you know what? if you still need x11 for some things, log in on a 2nd TTY to another user with an x11 session. you can then switch the active TTY to use the other. Though I admit, I have no idea how the 2 users' sound system work together
-
"I set my house on fire damn why did my house burn down its the builders fault."
at which part did they set the house on fire?
-
As an average desktop user, I've run into very little pushback on Wayland. Its made huge leaps in a short amount of time.
until you start using it and screenrecords dont work, multimonitor setups work once and then fail forever...
systemd,wayland, unity, ubuntuOne and all that stupid shit can right f off. -
hard disagree about the permissions. If I want to run closed source programs like games, discord, zoom or whatever, I like knowing they can't log all my keys, take screenshots or even run their own version of windows recall without my explicit permission
hard disagree. if your software is missing baaic functions, you shut up about roles and permissions or even force that crap on others.
-
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 cursor locking still happens in a handful of games for me - most work perfectly fine but sometimes i do end up running something with gamescope with the --force-grab-cursor argument to fix it.
this is when running games with either steam or wine/bottles/lutris.
strange that it happens in virualbox, i would think it "virtualizing" an entire display would fix issues like that. does virtualbox itself "grab" the cursor, or allow it to go off the screen by default? sorry i don't really know virtualbox, never used it much
-
Yeah it's at the point where i'm wondering if i still even need xorg. I'm still keeping it around just in case for now, but i could very easily purge it from my system anytime since i'm using nixos and all my xorg related settings are in a specific file. The main pet peeve i have with wayland is gaming related, and should hopefully improve when wine and proton go native wayland. I have a dual monitor setup and games always choose the wrong monitor by default, which means i can only use the resolution and refreshrate of the secondary monitor. I have a keybind to set the primary xwayland monitor with xrandr, which solves the problem, but it is a bit hacky. I also need to toggle vrr on and off with a keybind because it causes flickering on my monitor. It's a bit annoying but atleast it works, on xorg you can't even use vrr with multi monitor to begin with.
Have you tried running your games with gamescope?
-
Have you tried running your games with gamescope?
I think it does work, but from my understanding when nested inside another wayland session, thing like vrr don't work, which brings me back to the xorg problem, but my current workaround works for me, so now it's just a matter of hoping it will improve and become less tedious.
