[miloignis]

I recommend swapping your nix package to firefox-wayland -I've been using it for quite a while and it's been great. For me, it's been a huge improvement over X - thr lack of screen tearing when srolling and playing videos is huge.

If an app uses one of the normal GUI toolkits, they don't normally have to do anything crazy to support wayland, so I'd be suprised if you need to swap to a whole new ecosystem (and there's always XWayland for those that do).

[imiric]

Thanks, I'll try that, but the thing is that I haven't experienced screen tearing on X for many years now, on Intel, AMD or Nvidia cards, and even on high refresh rate displays (90/120hz). Sometimes when plugging in a second monitor I need to force full-screen composition with Nvidia cards to get rid of tearing, but I can always set this permanently in a config file, I just haven't gotten around to it.

I really haven't had major gripes with X for many years. It mostly just works, and is rock solid. Long gone are the days when you had to manually craft the perfect config file depending on your setup. It also works great with multiple monitors, though I think there are still some color management issues, which don't particularly bother me, and lack of HDR, obviously. Plus the client/server architecture is super useful, to this day. IME Wayland feels like a usability regression, forcing me to change many of the programs I use, and it has critical issues, which seemingly only affect me...

[kaba0]

You don’t notice screen tearing on normal usage with most desktop environments on X due to them using compositors. Try disabling it, or alternatively, to just play a high-resolution video on a high-res screen. The latter will often have artifacts.