Why is GNOME and KDE against X11 in this meme? Did they announce they are going to drop support for X11?
I’m surprised there are so many comments about the user experience for Wayland and X11. Unless you are programming for Wayland and X11, or are doing a lot of remote connection, you will not be able to tell much of a difference between the compositors other than package support differences. Im glad that there is an effort to move away from the X11, working with xlib is pretty archaic.
I switched to Linux roughly two years ago from Windows and I have absolutely no idea what all these comments are talking about. CachyOS and everything that I need just works. In fact, one of reasons I ended up on Cachy was because at the time, with my very limited understanding, it was one of the only ways I could get HDR to work.
Now that it at least supports my multiscreen, multi UI scale setup, it feels like Wayland is what all DE’s want to be. It’s so smooth and fast, and can always impose it’s will on all the windows. What do you mean this window won’t minimize and always stays on top?? WAYLAND SMASH. There I fixed it.
It feels very luxurious and decadent to have a DE that is so frocking good and reliable.
Aaaaand… GNOME still haven’t implemented server-side decorations.
Yeah GNOME is sabotaging Wayland now more than anything
I love the benefits of Wayland (display scaling, negative coordinates, hdr) but wish it had anything remotely as useful as xrandr (I have a 768x1024 16:9 plasma tv).
wrandr?
Wayland is so smooth. When I go to my friends house and use mint I’m instantly reminded how shit x11. Screentearing on the desktop, cmon what year is this.
If you’re getting screen tearing, it’s not X11’s fault. It’s the graphics manufacturers putting speed over stability.
I had an old Nvidia card that I never had a problem with under X11. The moment I upgraded to an AMD card, screen tearing, screen tearing everywhere.
To fix, you generally need to slap a small config file into /etc/X11/xorg.conf.d that tells the graphics driver that slow and steady wins the race.
The AMD solution literally contains the line
Option "TearFree" "true". Ridiculous.Link to one of many sites providing the full solutions: https://linuxjunkies.org/guides/fix-screen-tearing-on-linux
Wayland is so smooth
My plasma desktop is very noticeably slower and choppier with Wayland. The most visible example is when I switch workspaces and instead of the animation taking a fraction of a second it takes a second or two. It honestly feels like my laptop (which isn’t that old) was aged a decade by simply switching to Wayland.
I moved from X to Wayland when Fedora dumped X, and the first weeks were a pretty unstable experience (mainly because the Nvidia drivers still had some issues after implementing explicit sync), while performance never was an issue. Nowadays all of those problems are solved. Desktop streaming works fine with both pipewire and through whatever Sunshine uses, game FPS are comparable to Windows with some variation depending on title, and my desktop experience is buttery smooth.
I thought Cinnamon finally added Wayland support now? Anyway I had the same experience. Using Mint is how I realized 90% of distro recommenders on reddit and Lemmy have 0 fucking clue what they’re talking about
They added experimental support and i think they made it mostly functional in the upcoming release but dont quote me on that last bit
Ngl I have no clue which one I use. I was experimenting with them a year ago but I cannkt say which one I settled on.
What is the origin of this meme? Why do they want to kill this poor man who presumably lives there and just mowed the lawn?
Apparently the original:
The edit looks less edited than the original.
The joke is x.org (xwayland) is made by the same people that make wayland. Other x11 implementations often don’t support features that people ascribe to x11 as a whole.
Wayland doesn’t work on my little bro’s PC, graphics card is too old
As a person who doesn’t really give a shit. I’ve even forgotten that I’m on Wayland. Everything I need works and that’s all that matters to me. Y’all can keep your wars to yourselves
A lot of people just use Windows and everything they need works. And a lot of people like to customize things and use non-standard tools (quite common among Linux users, actually). It’s a bit silly to say “my setup works, I don’t know what people are complaining about”. Well, different people have different setups.
I’m not an obstructionist but having been forced in to Wayland by plasma 6.8 it is frustrating that orcaslicer just crashes unless I tell it to run in xwayland and desk flow requires being on unstable to work with my clipboard and discord canary just shares audio from my whole desktop instead of from just my game and AGHHH I just want my things to work! So frustrating
Both orcaslicer and discord audio sharing work properly for me on Wayland. Are you sure Wayland is the issue?
It’s usually not as simple as is Wayland the issue or not in my experience. Wayland and the wm/DE and the application all have to get along and it gets along better with some than others. For a variety of reasons. I had an issue with gtk on niri where specific applications would not open up and I had to do a bunch of tweaking. It did eventually work, but it really should have just worked automatically. Wayland was getting instructions from the app that it didn’t know what to do with and instead of it trying to use xwayland instead it was just failing. A lot of the problems come from the fact that X11 is OLD and because its OLD it has taken the time to work out so many random little potential issues. Wayland is new enough that sometimes it just runs into stuff that it hasn’t been tweaked to work around yet. We’re in the polishing phase now tho so these will start to get worked out I think. It’ll just take time. X11 does need replacing as its convoluted as fuck but there’s a reason some people swear by it, and that is largely for this reason. It’s just got a lot of niche functionality that takes decades of dev time to fully flesh out.
I’ve had a bunch of issues with Orcaslicer and Wayland. Thankfully it’s currently working for me but the last year or so I kept having to switch back to X a lot for it.
Orca craches for me if I don’t force the language to be English by setting the LC_ALL variable
That’s awesome.
50% of what I use doesn’t work and I will respond to the Wayland knife with C4.
I mean, let’s be honest. Most of people online came running with their pitchforks whenever someone said anything good about xorg or forked it. So, I guess most of them got what they deserved. Not you, of course 😂
Could you give some actual examples of the things that don’t work? I hear people say this a lot, but then they basically refuse to answer what’s not working. There was definitely a lot of wailing pain when it first transitioned, but these days, at least on plasma for me, I haven’t found anything that doesn’t work anymore. other than of course perhaps just some vague abandoned software that wants to do something crazy with the display
Plasma does solve some problems itself but: screen recording, global hotkeys, clipboard management to name a few. They all have “solutions”, it just sucks to be made to jump through hoops sometimes. There’s a lot of desirable things in x11 that while crusty worked well, like xrandr and being able to script monitor config. It is niche! But if you used it, it’s annoying to be forced off it
Here is a (biased but decent enough) list https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277
I guess those 3 are solved by KDE then. I only know Wayland through KDE and the 3 work perfectly fine for me, I didn’t even have to think about them when I used them.
What exactly about these three? I’m really curious to understand.
I never used X knowingly: by the time I’ve started understanding Linux more or so, I’ve been on Wayland already. So, in a way, I can say I never used X, even being on Linux on and off for almost two decades.
Say, screen recording. It just works for me on Sway (I use
wf-recorder) and it just works on Gnome. I have never thought of it as being broken. I could have missed anything though. Not something I use very often.What global hotkeys do you mean here? Mine work in all apps. So, I assume they’re global. Or is it something different?
Not sure about clipboard: it just works too. There’s this ‘middle mouse click’ shit that I hate, as I accidentally paste some unnecessary information into, say, email. Upon scrolling, and accidentally pressing the scroll wheel. I’d love to disable it globally, but it just there, working. I assume that’s a feature for some folks, but I passionately hate it and have no use for.
Not OP, but wanted to address some questions:
EDIT: I just realized in the linked gist they’re basically complaining Wayland doesn’t have “builtin” support for things like keylogging, and generally uses portals for features. Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?
Screen recording works, I think it’s only existing X software that doesn’t. In my experience there’s still some jank and limitations that might or might not be related to Wayland. After a few days of runtime with periods of sleep mode, screencasting through the portal seems to break until pipewire is restarted. I don’t know if there’s a way to capture an application and its audio automatically.
Global hotkeys refer to hotkeys that can be activated while the application isn’t focused. Wayland has global hotkeys, but some people don’t like the implementation and refuse to use it. OBS, for example, has an unofficial plugin implementing them, but the actual project refuses because they can’t display and set hotkeys from their own setting menu, and have no good way to support multiple profiles with separate bindings.
I also don’t know what they mean by clipboard management, but I do know there’s some jank. As a weirdly specific example, when playing Minecraft with patched glfw with native Wayland support, pasting into chat doesn’t work correctly, it seems to always paste the text that was in the clipboard when the game was opened, and not update when copying things from outside the game (but I think it works when copying something inside the game itself). I don’t know if this is an actual Wayland issue, or a case of a broken client implementation, but the lack of software support is still a type of issue.
Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?
Kind of. For a long time a mainstream setup like Gnome on Wayland lacked features because they weren’t yet incorporated into Gnome. But more generally, Wayland deliberately didn’t implement a bunch of features that X had, or had external things that accomplished. That pushed the responsibility for implementing it onto each and every window manager. Smaller WMs that would have had all of those features for free on X now have a big burden to achieve the same bar on Wayland, and so many don’t manage it. That’s due to the choices that went into Wayland.
Regarding the clipboard - there are practically 2 clipboards, i can paste different things based on whether i used ctrl-c/v or selecting text with the mouse and middle-clicking. I often fall into this trap, anf i would prefer it to be unified.
X11 still works better for me. I also can’t stand how my windows just pop all up in the middle of my screen on a single virtual desktop. On x11 they remebered their place. I also had better gaming performance with Manjaro + x11 instead of catchyos + wayland.
I solved that with window rules - every window i open on the regular or on system boot has its place on one of my virtual desktops. Also helps with the “now where did i put this thing last time”-effect i often suffered.
CachyOS + KDE here. My windows remember their place
x11 + Manjaro frame delivery was so bad I literally had to use Windows for gaming to not get sick. I don’t know why, I tried to fix it…
Tiling window managers!
I don’t disagree but this should not be the only solution for “remember where I put you last”
It’s little things for me, like how the first keystroke on the lock screen is part of my password entry with X11, but not with Wayland. Subtle changes in new window and focus behavior. I do still want a persistent bar, with a window list, tray, clock, and menu, but I think I’m going to switch to something like Ratpoison or i3; something tiling with good keyboard control.
The first keystroke thing sounds like it comes from your choice of dispkay manager. SDDM takes the first keystroke for example.
Don’t think that’s wayland. I’m using kde plasma and wayland, and first keystroke is definitely part of the lock screen password.
I have 2 fedora plasma instances and both of them miss the first character when I enter the password on the lock screen. It’s very annoying
That might be the display manager. Ly takes the first keystroke as well. I think SDDM does it too
im newbie to linux, and im using linux mint xfce, and i dont understand the meme hehe
you’re using fhe good old X11 then
In new versions, xfce experimentally supports wayland.
experimentally, only. they’re vibecoding xfwl4 and it’s set to come out in years.
Me too brother, me too. The command line is scary, but powerful, only if you know the correct incantations. You look those up in the tome labeled “Google”
i only use sudo apt update && sudo apt upgrade, and reboot lol, even when i turn off my laptop i use the mouse
This is completely fine. No need to use the terminal if you feel more comfortable using the mouse. I would only recommend to substitute upgrade for full-upgrade in your command. This really installs all available updates even if it requires to install new dependencies.
If you squint, it looks like Wayland is stabbing itself lol.
Also literally just waiting for wayfire and XFCE to become stable and I’ll switch off from Compiz.
Biggest issue with Wayland is/was the lack of feature parity with X11 and the painfully slow development time (I still argue Wayland only became viable start of 2025 after a bunch of major PR merges).
I know how LongtimeUser4 feels. His use case is ludicrous, sure, but xkcd’s ideas don’t come out of nothing.
I am dreading trying to rewrite my scripts that currently rely on
xdotoolandwmctrl. When last I looked into it, the equivalents didn’t cover the features I use, and the rationale from Wayland seems to be “why would you want to do that, old man?”I was the old person for the longest time but then I learned how ridiculously insecure the clipboard system in x11 is and I was suddenly like “oh would you look at the time, it’s wayland o’ clock already”
So what you’re saying is you’re pro murdering children???
(disclaimer/context: see alt-text from the linked comic)
I still use a x11 session for xdotool sometimes. That tool is so awesome
What features do you use? I was able to replicate just about everything I do with ydotool. It’s admittedly goofy to setup, but once you understand it, it works fine.
ydotoolwas still in its infancy when I last looked and I haven’t wanted to look again because I suspected that the situation would not have changed.So anyway, I’ve just woken up and am too dopey to care, so I went and looked.
ydotooldoes not do what I want.My scripts move, resize, change the title of, and sometimes even ask a window to close (
wmctrl -c).As best as I can tell, I have to hope that my DE provides something that will do some of what I want, or else write generic code that figures out where a window is on screen and makes exactly the right mouse movements and clicks to resize a window or close it, which is highly non-trivial. And changing a window title would appear to be impossible.


























