From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
X11 because Discord is unusable for me on Wayland, and I use it every day.
Edit: I recently switched to a 7800 XT (was using a 3080), and the discord problem was either solved since the last time I tried it, or not being on nvidia helps - no more weird input lag etc. in discord, so I've moved over to Wayland finally.
X11. It just works for me, no reason to switch. Plus I exclusively use Xfce or MATE which as far as I know do not have Wayland support.
Same here; I'll switch whenever Xfce does. Which, by the way, will probably happen sooner than expected, by the time 4.20 comes out. All the core apps & the development version of the panel already work on Wayland.
Unless you are on NVidia or need X11 specific things (E.g. a lot of the accessability stuff) I would go for Wayland, it still has some issues but so dose X11 and Wayland is simply the new display server from the xorg foundation because X11 was impossible to properly update by now, it has far too much lagacy code and didn't get any new version in ages for that reason.
Wayland is not a display server, it's just a protocol. The compositor acts as both window manager and handles the graphics card interface.
Both of them have issues depending on the setup. X11 has worked flawlessly in my experience. Wayland has worked the same for most.
Personally, Wayland still has some growing pains, especially in regards to Input handling (mouse, keyboard, etc). In X11 it was "trivial" to edit one file and have the settings stick across different WMs (switching from DWM to i3, etc.) There's no standard for this with Wayland since it's up to the compositor to handle these things, meaning you're relearning how to do something as basic as setting pointer speed each time you try a new compositor. This is my only real fair gripe about it currently, as the rest of my complaints are just due to how young a lot of the Wayland-specific tools are - this will improve with time.
X11 because KDE cut some features for Wayland (some that will be cut in Plasma 6 X11 too, yay) and some apps just don't support wayland for technical reasons.
x11 cuz xfce also .. i want a just working system^^
I still use X11 because one of my necessary voip apps (mumble) doesn't yet support wayland's method of global hotkeys.
Otherwise I don't particularly care one way or the other.
X11 for xdotool. ydotool doesn't support (& can't really support with it's current architecture) retrieving information like the current mouse location, current window, window dimensions & titles. Also, normal (unprivileged) user ydotool use requires udev rules or session scripts and/or running a ydotool daemon & many distros don't yet ship with this Just Working.
X11 for Alt-F2 r to restart Gnome Shell without ending the whole session. This is a useful workaround for a variety of Gnome bugs.
Wayland. It's super smooth and supports new display features.
Everything works, but I don't really use global keyboard shortcuts.
X11 because my current setup on Wayland crashes constantly, otherwise always Wayland.
Wayland, works better with games. Unless it's star citizen, then x11 because it somehow breaks the elevators
X11 because i3wm
Honest question: what does i3wm that swaywm doesn't?
Honestly, I never heard of it before, so I checked to see what it is. I wrote a pretty neat config for my i3wm and to this day am so comfortable with it that I would never change it.
From my understanding after a look, it is pretty much i3wm for Wayland. If my config works well with it, I might give it a shot.
Currently on Wayland with AMD. Only issue is I cannot Steam remote play without relogging into X11, but that is a very infrequent occasion.
Everything else (mostly gaming) works very well for me.
FWIW remote play is fine on GNOME here.
KDE here and definitely was not fine last I tried. I'll keep messing with it though out of curiosity.
You can use the pipewire capture to do the remote play on wayland session.