After a few years on Windows I recently returned to Arch Linux which I previously used with the i3 tiling window manager, and am now using Sway (a Wayland port of i3). It generally works well, but there are
many applications that I have to fiddle with to get to work properly.
Firefox is still X by default, meaning to me most significantly no high-DPI support or precise scrolling. You can force it to use Wayland via the MOZ_WAYLAND_ENABLE environment variable, but it still has definite issues, like popup windows not being marked as popups, with effects like notifications being added to the non-floating windows and taking focus, rather than floating in the corner of the screen undecorated. (I use Nightly and am test-driving the process-per-site thing and it’s currently got other issues that are probably Wayland-specific, but that’s what you get for using prerelease stuff.)
Audacity has utterly crippling issues when run Wayland-native (its default). So I have a wrapper script that first clears the WAYLAND_DISPLAY environment variable so it will use XWayland, where it has fewer issues (it’s still pretty bad in places, e.g. all popup windows are start out at the minimum possible size and have to be resized before you can interact by anything other than keyboard, but I’m running high-DPI XWayland patches and I suspect this is at least partly due to bugs in that).
Krita I need to set QT_SCALE_FACTOR to match my XWayland scaling (a high-DPI thing). Note that I can’t set this globally, or else Qt apps that can run under Wayland (e.g. Zeal) will be huge.
cq-editor (CadQuery) crashes in Wayland and must be run with `--platform xcb` or with WAYLAND_DISPLAY unset. (Upstream’s distribution is built against a Qt that is not Wayland-enabled, so the problem actually doesn’t arise there, but if you build your own it’ll probably be Wayland-enabled.)
Zoom has taken to crashing on joining meetings under Wayland, and only implements some GNOME-specific screen sharing rather than xdg-desktop-portal screen sharing which is, I believe, what everyone else settled on—showing the internal fragmentation problem of Wayland. So because of the crashes, I run Zoom under XWayland, not even losing screen sharing because it was already broken. (Firefox and Chromium do screen sharing without any trouble, but only of whole outputs, not individual windows.)
But on the other hand, a few days ago I started i3 so I could do screen sharing on Zoom (of a second display, HDMI-A-1, 1920×1080@60Hz; main display eDP-1 being 2560×1440@165Hz), and ugh, the tearing! Full screen updates in Alacritty pretty consistently do the top half in one frame and then the bottom half in the next frame, and the block cursor moving while typing is super glitchy. I had forgotten how bad this stuff was because Wayland does it perfectly.