What’s always funny to me when someome brings up missing features of Wayland is how, apparently, the missing features of X11 are getting pushed under the table or somehow also blamed on Wayland in some twisted way.
Like, holy shit, compare the display settings of KDE on a modern display between Wayland and X11. My laptop didn’t even show a third of all options anymore.
Sure, it will be nice once Wayland can do a few things (better), the current development push surely helps. But it’s not like X11 can do everything either.
Yeah. “Feature parity or get out”, like dude we’re long past feature parity.
Wayland supports so much more stuff than X11 does, and what does X11 have that Wayland doesn’t? X forwarding? Just use a modern remote desktop solution, all X forwarding was doing in “modern” times (read: the 21st century) was streaming pixels anyway, just less efficiently than modern remote desktop.
People who like multi window gimp must be a very special kind of nerd. I used it before single window mode was added, but when it was I never looked back. Positioning each subwindow in a way that didn’t suck was such an absolute pain
It’s not a pain if you use a tiling WM, and doesn’t KDE remember and restore window positions yet?
alias hc=herbstclient
# GIMP# ensure there is a gimp tag
hc add gimp
hc load gimp '
(split horizontal:0.850000:0
(split horizontal:0.200000:1
(clients vertical:0)
(clients grid:0))
(clients vertical:0))
'# load predefined layout# center all other gimp windows on gimp tag
hc rule class=Gimp tag=gimp index=01 pseudotile=on
hc rule class=Gimp windowrole~'gimp-(image-window|toolbox|dock)' \
pseudotile=off
hc rule class=Gimp windowrole=gimp-toolbox focus=off index=00
hc rule class=Gimp windowrole=gimp-dock focus=off index=1
I still use X forwarding.
It works just fine using xWayland, and X forwarding has always been so janky there is no chance to notice any difference caused from using xWayland instead of native.
It will surely take many years and well established wayland native remote tunneling before anyone thinks of ditching xWayland.
Yeah. “Feature parity or get out”, like dude we’re long past feature parity.
Ok, replace the xfce/KDE wm with something like i3 and then keybind all of the commands that aren’t wm specific through a global hotkey daemon like sxhkd.
I can’t copy/paste from a terminal program to a GUI program under wayland without jumping through hoops and configuring every individual program to use some variant of a DE-specific utility that bypass wayland’s model to peek/poke into the clipboard.
That’s not a minor feature to me. And in my (and probably some other people) case, trading basic copy/paste for not-yet-implemented differential DPI scaling does not sound too great.
Some people are adamant to not switch, but I swear some people are so adamant to force everyone else to switch without even considering that their use case might not match other people use case, it’s infuriating. It’s not like me staying on X will degrade everyone else’s experience of the new shiniest thing.
Distribution moving to wayland might be good in the very long term, but for now, when you have a 3080Ti (a relatively recent card) and it breaks basic desktop composition when switching to wayland, telling people “just throw it out and buy another card instead of keeping your currently working system” is not going to help anyone.
What are you talking about? You can copy-paste from Terminal programs to GUI programs and vice-versa like everywhere else (with the terminal of course needing CTRL + SHIFT + C / V, which as we know is historical to Unix terminals). I’m doing that for years, so does my family. It works just fine.
And bringing up Nvidia now really is bending down backwards to paint Wayland as bad while it’s painfully obvious it’s the driver’s fault. We all know the classic Nvidia driver sucks in more ways than one and loves to break, even Nvidia knows that and works on a replacement. That’s not Wayland’s fault.
Thats not entirely true. wl-copy exists and I use it, but it’s not fully there yet. Things like slackadays/clipboard are still fucking around with weird Wayland issues.
I’d like better clipboard support, but alias c=wl-copy is good enough most of the time for me. And it works in neovim as well.
Yeah, I know of such “solution”. But what is the point of forcing the change when it doesn’t bring me tangible benefits, brings significant downsides, and only some of these downsides have half-useful workarounds?
I have no problem with whether wayland existing or it becoming the new standard, but forcing people to move in these circumstances seems a bit silly, especially when some issues stem from people having hardware from one manufacturer that represents around 75% of general consumer systems (according to Steam survey, which might or might not be representative but sure brings a lot of people).
Thankfully, at least with the distributions I use, switching back and forth is trivial. But given the circumstances, I don’t really understand the extremely heavy push.
While it’s certainly winded down over time, XOrg is still maintained. Last fix was released in september 2025. Is it enough? It never is. But that’s not really an argument to move from “working” to “not working as well” for now.
What’s always funny to me when someome brings up missing features of Wayland is how, apparently, the missing features of X11 are getting pushed under the table or somehow also blamed on Wayland in some twisted way. Like, holy shit, compare the display settings of KDE on a modern display between Wayland and X11. My laptop didn’t even show a third of all options anymore.
Sure, it will be nice once Wayland can do a few things (better), the current development push surely helps. But it’s not like X11 can do everything either.
Yeah. “Feature parity or get out”, like dude we’re long past feature parity.
Wayland supports so much more stuff than X11 does, and what does X11 have that Wayland doesn’t? X forwarding? Just use a modern remote desktop solution, all X forwarding was doing in “modern” times (read: the 21st century) was streaming pixels anyway, just less efficiently than modern remote desktop.
Multi window apps are still broken, and the wayland protocol guys have been dragging it for more than two years
Honestly which app do you use that makes use of multi window rendering?
The main one is KiCAD (electronics design).
They have a good article on the challenges they’re facing on Wayland, worth a read https://www.kicad.org/blog/2025/06/KiCad-and-Wayland-Support/
I don’t, but some people like multi window GIMP, and apparetnly several applications in the automotive (kiCAD for example) and scientific field
People who like multi window gimp must be a very special kind of nerd. I used it before single window mode was added, but when it was I never looked back. Positioning each subwindow in a way that didn’t suck was such an absolute pain
It’s not a pain if you use a tiling WM, and doesn’t KDE remember and restore window positions yet?
alias hc=herbstclient # GIMP # ensure there is a gimp tag hc add gimp hc load gimp ' (split horizontal:0.850000:0 (split horizontal:0.200000:1 (clients vertical:0) (clients grid:0)) (clients vertical:0)) ' # load predefined layout # center all other gimp windows on gimp tag hc rule class=Gimp tag=gimp index=01 pseudotile=on hc rule class=Gimp windowrole~'gimp-(image-window|toolbox|dock)' \ pseudotile=off hc rule class=Gimp windowrole=gimp-toolbox focus=off index=00 hc rule class=Gimp windowrole=gimp-dock focus=off index=1Uh huh. You do you.
It’s not cool to write someþing as if you’re quoting me saying someþing I didn’t.
I literally copied þat off þe herbstluftwm web site. I had to write, tweak, and debug noþing about it.
I still use X forwarding.
It works just fine using xWayland, and X forwarding has always been so janky there is no chance to notice any difference caused from using xWayland instead of native.
It will surely take many years and well established wayland native remote tunneling before anyone thinks of ditching xWayland.
Ok, replace the xfce/KDE wm with something like i3 and then keybind all of the commands that aren’t wm specific through a global hotkey daemon like sxhkd.
https://github.com/waycrate/swhkd ?
I could never get it to work.
I can’t copy/paste from a terminal program to a GUI program under wayland without jumping through hoops and configuring every individual program to use some variant of a DE-specific utility that bypass wayland’s model to peek/poke into the clipboard.
That’s not a minor feature to me. And in my (and probably some other people) case, trading basic copy/paste for not-yet-implemented differential DPI scaling does not sound too great.
Some people are adamant to not switch, but I swear some people are so adamant to force everyone else to switch without even considering that their use case might not match other people use case, it’s infuriating. It’s not like me staying on X will degrade everyone else’s experience of the new shiniest thing.
Distribution moving to wayland might be good in the very long term, but for now, when you have a 3080Ti (a relatively recent card) and it breaks basic desktop composition when switching to wayland, telling people “just throw it out and buy another card instead of keeping your currently working system” is not going to help anyone.
What are you talking about? You can copy-paste from Terminal programs to GUI programs and vice-versa like everywhere else (with the terminal of course needing CTRL + SHIFT + C / V, which as we know is historical to Unix terminals). I’m doing that for years, so does my family. It works just fine.
And bringing up Nvidia now really is bending down backwards to paint Wayland as bad while it’s painfully obvious it’s the driver’s fault. We all know the classic Nvidia driver sucks in more ways than one and loves to break, even Nvidia knows that and works on a replacement. That’s not Wayland’s fault.
Thats not entirely true.
wl-copyexists and I use it, but it’s not fully there yet. Things like slackadays/clipboard are still fucking around with weird Wayland issues.I’d like better clipboard support, but
alias c=wl-copyis good enough most of the time for me. And it works in neovim as well.Yeah, I know of such “solution”. But what is the point of forcing the change when it doesn’t bring me tangible benefits, brings significant downsides, and only some of these downsides have half-useful workarounds?
I have no problem with whether wayland existing or it becoming the new standard, but forcing people to move in these circumstances seems a bit silly, especially when some issues stem from people having hardware from one manufacturer that represents around 75% of general consumer systems (according to Steam survey, which might or might not be representative but sure brings a lot of people).
Thankfully, at least with the distributions I use, switching back and forth is trivial. But given the circumstances, I don’t really understand the extremely heavy push.
I don’t think anyone’s forcing anyone to do anything. But not a lot of people are stepping to to maintain X
While it’s certainly winded down over time, XOrg is still maintained. Last fix was released in september 2025. Is it enough? It never is. But that’s not really an argument to move from “working” to “not working as well” for now.
I thought most of the maintenance went towards Xwayland, though I don’t follow it that closely