Wayland has a bright future ahead: The move from Xorg to Wayland had a rough start, but things have improved, and there is an exciting roadmap for the future.
Every X11 application runs in the same Xserver, so there's no isolation which would be a massive incentive for adoption.
Attempting to run anything Wayland inside a Docker container across the network is doomed to fail. RDP, VNC and the rest of these are a massive loss in functionality compared with X11 across the network.
I want this to work, but so far it just doesn't.
In case you're wondering, try running a GUI application on a remote server side by side with one running on another server on the same display and copy/paste data between the two.
Nothing else compares. I’m begging for an explanation on why you’d go out of your way to shame another person for what software they prefer. I’m terrified it’s related to being unable to think for yourself.
If that breaks your brain, I've got one for you: herbstluftwm for life.
I want no configuration file. The WM should run a program that configures and sets up everything. Not even as much a config as i3, or Sway. Nothing about the compositor should be configured or set unless it's through a CLI client call.
There are dozens of compositors, pretty ones like Hyprland and novel ones like Niri, but always with the bespoke configuration files in whatever random config file format the maintainer has a thing for.
River looks similar to herbstluftwm in the configuration area. I did try it a few months ago; I don't remember why it didn't work out - lacking multi-monitor support, maybe? But since it's in active development I'll have to try it again.
After using Linux almost exclusively for over 20 years and at some point used nearly all of the desktops and window managers that exist for X; and having come to the conclusion that - in general - configuration files for long-running services are bad design, and that nearly all services should be runtime-configurable with tooling, I just won't use a compositor with a static configuration. Hot reloading is a work-around hack. I3's live restart is a pretty decent solution, and i3-mesg is close, but the gaps eventually become obvious.
That screenshot of glxgears is giving me flashbacks of editing and re-editing my XF86Config trying to get my video card to give me some modicum of performance.