I don’t understand the “applications not ready” problems - Apps that don’t support wayland use X11 anyway?
Firefox behaves really troublefree with MOZ_ENABLE_WAYLAND=1 set - same goes for Chromium and Vivaldi with the wayland-option set to “Auto” which enables their native wayland mode when run in a wayland environment.
But I have only AMD card’s, not an antiquity from Ati or a proprietary-driver-one in green.
I only play World Of Warcraft with Lutris and some occasional GTA V, but that also works without issues.
For example, Flameshot doesn’t work properly on Wayland, Zoom doesn’t support screen sharing on Wayland in certain situations, etc, etc
There are other applications that exhibit strange behaviours under wayland. For example, anything that needs to intercept keyboard commands exclusively can no longer do so. While that sounds great in theory, it means that if you work in a VM or a remote session of any kind those applications can no longer use hotkeys because they are grabbed by the host.
emphasized textI did not do any screensharing yet , but I have to use a remote session for work, and there everything works, including keyboard shortcuts and hotkeys (it works both in KRDC and xfreerdp)
I just tried to share an application window in Jitsi Meet (the Service that Rocket Chat uses) and it works just fine. Sharing the entire screen is only a black screen, but for privacy protection reasons, we are not allowed to share entire screens anyway - but yeah, if you need to that bug kind of sucks.