linuxmemes

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.

Wayland is the new protocol and will be the one that everything uses in the long run

If Wayland works for you, then that's great, don't use X11

The main reason you'd want to use X11 these days is for compatibility. But that's getting less and less of a concern as time goes on

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.

If you have no issues with Wayland, keep using it. You aren't missing anything.
Linux is a vast space, and some people have use cases that aren't covered by Wayland, yet.
So they still use X.

They use it cause their desktop does not support wayland yet or their Nvidia card causes issue with it, potentially since they are using an older driver.

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

Nothing, unless you really want to use a DE that's still lacking behind in its adoption. There are a few tools that still only offer early support for it (like RustDesk), but otherwise Wayland is a way better choice these days. However if you got an Nvidia GPU and need to use the proprietary driver you might be forced to still use X11. Their pile of garbage still routinely bugs on Wayland, and given their work on NVK I doubt that thing will ever get fully fixed.