gasp

If you're fine with Wayland, go with Wayland. There are lots of reasons still that people might prefer X11 but the list has been getting shorter.

• The security model of Wayland is more restrictive than necessary for many users and means things like screen sharing and desktop toys are harder and not universally implemented or doable.
• Wayland effectively requires many things to be handled by the same process, preventing traditional modular environments (e.g. separating window manager from compositor no longer possible)
• Explicit compositor support required for more features, meaning having a feature complete environment in small projects is much harder, and the design of Wayland tends to promote a few large desktop environments rather than many small window managers.
• NVidia's support for Wayland is still improving
• Wayland can't rotate your screen to be on an angle to maximise the length of a line
• Several programs I rely on don't support Wayland well yet
  • Steam doesn't stream from Wayland
  • Transparent bits of FreeCAD show the background instead of what's behind them
  • Code-OSS required a very silly workaround for decent font rendering, although I think this might have been fixed in electron

I also switched to use different Wayland compositors many years ago for my main systems, but there are also still reasons to use X11. These are mine:

• X11 forwarding, with that you can connect to another system via SSH (e.g. via ssh -Y) and just start a GUI app, and the window appears on your screen.
• Sharing individual windows via WebRTC, with Wayland compositors you can normally only share full screens. Xserver allows applications to directly capture the window content of others.
• Easily mirroring screens for presentations, with some Wayland compositors you have to capture one screen and then play it back on another screen, with X11 that is integrated into the xserver.
• Automation and keyboard macros, with X11 it is much easier to automate keyboard macros and customize keyboard mapping than on Wayland. See Xmodmap, etc. Same for mouse input. That is also a reason why implementing remote control software is more difficult with Wayland, see for instance RustDesk support for Wayland (works now, but still a bit experimental).

There might be some Wayland compositors that worked around that, but on X11 this was standard. But generally X11 provides these features for all WMs, and in Wayland they have to be implemented individually.

And some just are not supposed to work, for security reasons.

But all of this depends on your use-case. I sometimes even (can or have to) go without a Wayland compositor or X11 and render GUI directly via KMS/DRM.

Xorg literally has a option to disable tearing: Option "TearFree" "true. If that doesn't work and your compositor neither, fix your video drivers. Lookup Hardware Video Acceleration and similiar on Arch wiki.

I like XFCE4 but there is no compositor for it yet.

I remember when /bin/sh was the default shell, when you had to build grep from source. LILO was our bootloader. Dmesg was our seer. We made fire from a friction drill. Knapped our own blades from flint.

Simpler times.

Y'all are still using xorg?

I remember when loading a GUI in *NIX systems was frown upon and would get you judged by your peers…

"Story time" is just another word for "I'm showing my age"

It is a good way to know who's a Grey Beard

...who... IN THE FUCK!!! Reads Debian docs?

Arch are the true Linux docs, maybe Gentoo docs, worst case Ubuntu forums.

Run a ton of Debian, only time I check their docs is when I'm trying to remember what the current stable release is called.

Can it force apps to use iGPU when dGPU is on? It's one of the things I miss from windows and couldn't figure out on linux

I did xorg.conf from the example on Arch wiki and it worked. Then i did it the correct way from the official documentation and it didn't.

I mean, there was a point in time, quite some years back, when I had to do up modelines, but Xorg can generally handle things without an xorg.conf.

Do you really think ppl don't break their wayland setup? For example, some systems don't get a mouse cursor in wayland umless they switch the cursor to software rendering. To do that, they must often set an env var for the wayland process, but there is no standard way to do it. Half of them starts tinkering with their PAM and the others with their .profile . Sometimes this breaks every way to log in.

Still won't handle popup menu correctly, still won't allow copy/paste with CLI programs without using an extra, implementation-specific, piece of software, still won't allow some window to correctly detect their position.

Wayland might be interesting, but between blind haters and blind supporters, it's really annoying. Forcing people to switch while some basic features are "mostly working" is not helping.