As someone who actively uses a wayland compositor and has done so since switching to linux ~4 years ago, I often feel like I live in a different world from the authors of articles discussing its usability. Just to discuss a few points made about wayland's supposed inferiority:
> Wayland cannot do (or do well) tons of things:
> VNC server
> remote desktop
I don't regularly use either of these so I cannot attest to whether they work on wayland.
> SSH X forwarding
https://gitlab.freedesktop.org/mstoeckl/waypipe
> custom keyboard bindings
I currently have caps lock bound to esc
> numerous accessibility options
This is likely true
> legacy software
xwayland
> absolute desktop positioning
Once again, I'm running absolute desktop positioning right now
> screen sharing and recording
I just installed and ran obs, told it to use screen capture as a source, it recorded fine
> CAD/EDA tools
CAD software only runs on windows anyway. For KiCad, it's seemingly blocked on a window positioning protocol, which wayland will hopefully adopt soon
> Wayland cannot do (or do well) tons of things:
> VNC server
> remote desktop
I don't regularly use either of these so I cannot attest to whether they work on wayland.
> SSH X forwarding
https://gitlab.freedesktop.org/mstoeckl/waypipe
> custom keyboard bindings
I currently have caps lock bound to esc
> numerous accessibility options
This is likely true
> legacy software
xwayland
> absolute desktop positioning
Once again, I'm running absolute desktop positioning right now
> screen sharing and recording
I just installed and ran obs, told it to use screen capture as a source, it recorded fine
> CAD/EDA tools
CAD software only runs on windows anyway. For KiCad, it's seemingly blocked on a window positioning protocol, which wayland will hopefully adopt soon