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.
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.
Well, we’re currently in the process of porting apps away from Windows Server 2012 and CentOS 7.
What you’re describing is just how the industry works, not specific to Wayland.
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.
Edit: I will say, one thing I still hate about wayland is the sleep behaviour. The 2 x11 systems I still use work well for this, none of my wayland systems want to wake up from sleep nicely.
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, either the DE/WM you use has not implemented the protocols, or the app you’re 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.
I will never understand what is rough. Ive been using fedora kde for what … 2-3 years now? More?
2 years ago there were some issues with nvidia, but that is fixed now mostly.
I use it for work, there is an ocasional hiccup, that gets fixed next reboot, something like a terminal not resizing just right but … thats it?
People dont like change man, in the day and age when tech changes at breakneck speed, people dont like change
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.
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
Well, we’re currently in the process of porting apps away from Windows Server 2012 and CentOS 7.
What you’re describing is just how the industry works, not specific to Wayland.
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.
Edit: I will say, one thing I still hate about wayland is the sleep behaviour. The 2 x11 systems I still use work well for this, none of my wayland systems want to wake up from sleep nicely.
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.
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.
ive used all three on wayland without issues.
All of those things function on Wayland using the right protocols. If they dont work for you, either the DE/WM you use has not implemented the protocols, or the app you’re 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.