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.
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.
I’m not talking about copy/pasting from the terminal emulator, thank you very much. Just run VIM and have it copy/paste from the global clipboard without setting up esoteric, sometimes DE-dependent stuff, and you’ll understand.
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.
Sure. I did not say it was wayland fault. Or anyone else, really. I explained why some people could not “just move on to wayland already you nincompoop” with very tangible issues that still prevent them from doing so. Who is at fault is of no consequence here. If I switch to wayland, I lose features, I have a broken desktop, and throwing away thousands of equipment because “it’s the future” does not sound that great. It’s just a matter of fact. Whether it’s wayland’s fault, plasma’s implementation’s fault, nvidia’s fault, or anyone else’s is irrelevant to the user experience here.
People can’t go “stop using X and use wayland”, and ignore raised issues by saying “no, that issue you’re having is not a big issue”, “that issue you’re having is not wayland’s fault”, “that issue you’re having does not concern most people”, etc. And reading replies in this thread, it seems people have a hard time imagining circumstances beyond their own.
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.
It mostly did, yes. But when a big issue pops up, X still gets the occasional patch.
And, since this is a bit of a hot topic it seems, that sounds fair to me. X is the past, wayland is the future. I’m just annoyed at people glossing over the reasons not everyone can move on.
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.
I’m not talking about copy/pasting from the terminal emulator, thank you very much. Just run VIM and have it copy/paste from the global clipboard without setting up esoteric, sometimes DE-dependent stuff, and you’ll understand.
Sure. I did not say it was wayland fault. Or anyone else, really. I explained why some people could not “just move on to wayland already you nincompoop” with very tangible issues that still prevent them from doing so. Who is at fault is of no consequence here. If I switch to wayland, I lose features, I have a broken desktop, and throwing away thousands of equipment because “it’s the future” does not sound that great. It’s just a matter of fact. Whether it’s wayland’s fault, plasma’s implementation’s fault, nvidia’s fault, or anyone else’s is irrelevant to the user experience here.
People can’t go “stop using X and use wayland”, and ignore raised issues by saying “no, that issue you’re having is not a big issue”, “that issue you’re having is not wayland’s fault”, “that issue you’re having does not concern most people”, etc. And reading replies in this thread, it seems people have a hard time imagining circumstances beyond their own.
I’ve used this neovim keybind for years:
vim.keymap.set({'n', 'x'}, 'gy', '"+y') -- copy vim.keymap.set({'n', 'x'}, 'gp', '"+p') -- pasteI was able to copy/paste between nvim and other applications on sway, Hyprland, Niri and KDE on Wayland.
The global clipboard register + should also work in modern regular vim afaik.
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
It mostly did, yes. But when a big issue pops up, X still gets the occasional patch.
And, since this is a bit of a hot topic it seems, that sounds fair to me. X is the past, wayland is the future. I’m just annoyed at people glossing over the reasons not everyone can move on.