this post was submitted on 28 Jul 2025
93 points (89.1% liked)
Linux
8723 readers
421 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
These “Wayland will never come” articles completely ignore the fact that Wayland is here and has already won.
There are lots of issues with Wayland. They will be fixed, but if this was simply a list of things still needing to be improved, it would be useful.
But most Linux desktop users use Wayland already. It will be 90% in 2-3 years. With the exception of Mint, the big Linux distros already install to Linux by default. So almost every new Linux user starts on Wayland. Few will ever try X11. And if they did, the list of broken and impaired experiences on X11 will bring most back to Wayland.
It really does not matter if every x11 user switches to Wayland. The ecosystem does not need them.
But very few of even the hard core adherents will use an X server 5 years from now. Most normal users will not even use Xwayland. And the simple reason is applications.
Everyday there are more and more apps that are Wayland only. Before 2030, that list will include all GNOME and most GTK apps. Are people really going to give up all these applications because of some obscure advantage they perceive in X11?
Most the the faults the article cites are exaggerated or historical. But it is not worth arguing over the details. Wayland is the future. But it is already the present. It is sad really that the people writing these articles do not realize that they are already in the minority and have already been left behind.
This is a “Linux will never be ready for all UNIX users” article written in 1998. It is both true and irrelevant.
The only thing stopping me from switching is the fact TigerVNC server doesn't support it, I wouldn't be able to LAN remote into my workstation.
What do you mean by that? I'm using TigerVNC with wayvnc on sway
I currently use Arch/X11/KDE with TigerVNC, I remember there being issues half a year ago when I last checked it.
Can you share the contact of your copium dealer?
Because, really, this is one of the most disparagated stuff I've ever read this year.
Remind me 2030 if these issues I have get fixed:
https://github.com/swaywm/sway/issues/8000
https://github.com/swaywm/sway/issues/8001
https://github.com/swaywm/sway/issues/8002
https://github.com/swaywm/sway/issues/8191 I later learned the reason sway is using capabilities is to fix performance issues, which yeah still has several...
One issue the wayland proponents fail to notice is that the ecosystem itself is fragmented, you have several DEs/WM with their own implementations and bugs that will likely never be fixed.
I'm an i3wm user, my only option to switch to is sway, doesn't matter if some of the issues I have are fixed in kwin or mutter, it has to be fixed in sway.
Most desktop users use windows, and they are happy with that, why don't you stop using linux and move to windows?
https://aur.archlinux.org/packages/12to11-git
Doesn't remove the fact that wayland still sucks 😆
You want me to track the progress of 4 bugs in Sway? Such a powerful argument. How about don’t use Sway?
I did not fail to notice. I have another post here comparing compositors to web browsers. There is more than one by design. Long term, it is absolutely one of Wayland’s strengths. But ya, your experience is only going to be as good as the browser you choose.
For tiler lovers, Niri and Hyprland are both great. COSMIC is looking good but still Alpha. Plasma 6 is perhaps the best Wayland compositor at the moment.
Hilarious. Linux has been my primary desktop since the 90’s. You probably need to get off my lawn.
Even more hilarious. Looks like you found an even crappier Wayland compositor than Sway.
Amongst the long list of broken things in 12to11, my favourite is this: “has not been tested on window (and compositing) managers other than GNOME Shell”. GNOME is a Wayland first and soon to be Wayland only project. A project clinging to Wayland on X on GNOME is a perfect metaphor for the point I am making. Thank you for making my point so well.
By 2030, Xorg will be in the AUR and the only x server in the core Arch repos will be Wayback (Xwayland on Wayland).
Sounds like you will be using 12to11 to run Wayland apps on i3 on XWayland on Wayback (Wayland on X on Wayland). Good times.
You seem to think I am telling you to use Wayland though.I don’t care what you use. My point is that everybody else is happy leaving you behind. Keep using X. You can switch to the Dillo browser too if you want. LMAO.
Very subtle “Arch, BTW”, BTW. Nice.
For everybody else, here is the project you linked to. It is a fun little project.
https://git.linuxping.win/12to11/12to11
4 bugs discovered in less than 48 hours of use.
I don't, I'm on i3wm as result.
Tried hyprland as well, it is useless.
Hyprland is such a meme, that the config file doesn't allow chaining multiple actions to a single keybind, you have to instead repeat the same keybind several times in the config lmao.
Also in hyprland you cannot move a floating window between displays using the move left and right commands, this is because the action does not move the window in that direction but rather to the left or right side of the display, meaning the window gets stuck at the border between the two displays and does not move anymore 😹
Also this whole disaster that I was a victim of, the documentation was insanely outdated and someone had to repeat the dev about the issue: https://github.com/hyprwm/hyprland-wiki/issues/242
It works lol
My issue is not if an app works on X11 or wayland, but the terrible implementations that wayland that lack even the most basic features.
And once again doesn’t remove the fact that wayland still sucks 😆