this post was submitted on 11 Nov 2025
510 points (89.6% liked)

linuxmemes

29831 readers
798 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Natanox@discuss.tchncs.de 119 points 2 months ago (2 children)

    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.

    [–] turdas@suppo.fi 85 points 2 months ago (4 children)

    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.

    [–] Redjard@lemmy.dbzer0.com 28 points 2 months ago* (last edited 2 months ago) (1 children)

    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.

    [–] First_Thunder@lemmy.zip 21 points 2 months ago (1 children)

    Multi window apps are still broken, and the wayland protocol guys have been dragging it for more than two years

    [–] bobo@lemmy.ml 7 points 2 months ago (2 children)

    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.

    [–] turdas@suppo.fi 1 points 2 months ago (1 children)

    If you're waiting on Wayland to reimplement the thing that made X11 a monolithic unmaintainable mess, you'll be stuck on your rotting platform from the 80s for a while.

    [–] jojowakaki@lemmy.world 2 points 2 months ago

    I switched to Wayland. I think I have almost everything working except keepassxc's global hotkey and autotype. Also certain apps like ardour, I have to manually break components off from the main window and move to different monitor to get the "multi monitor" functions going. This I know they have been trying for 2 years now, anyday now.

    [–] cley_faye@lemmy.world 4 points 2 months ago (2 children)

    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.

    [–] Natanox@discuss.tchncs.de 9 points 2 months ago (1 children)

    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.

    [–] cley_faye@lemmy.world 3 points 2 months ago (1 children)

    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.

    [–] ne0phyte@feddit.org 3 points 2 months ago

    I've used this neovim keybind for years:

    vim.keymap.set({'n', 'x'}, 'gy', '"+y') -- copy
    vim.keymap.set({'n', 'x'}, 'gp', '"+p') -- paste 
    

    I 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.

    [–] PlexSheep@infosec.pub 5 points 2 months ago (1 children)

    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.

    [–] cley_faye@lemmy.world 1 points 2 months ago* (last edited 2 months ago) (1 children)

    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.

    [–] urandom@lemmy.world 1 points 2 months ago (1 children)

    I don’t think anyone’s forcing anyone to do anything. But not a lot of people are stepping to to maintain X

    [–] cley_faye@lemmy.world 1 points 2 months ago (1 children)

    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.

    [–] urandom@lemmy.world 1 points 2 months ago (1 children)

    I thought most of the maintenance went towards Xwayland, though I don’t follow it that closely

    [–] cley_faye@lemmy.world 1 points 2 months ago

    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.