I don't have a huge amount of experience with Krita's Wayland performance because the situation on Wayland is still sub-optimal for art in general. Tablet support has gotten much better, but configuration per-app or tied to the desktop environment still seems to be a big issue. The idea that my tablet configuration might stop working if I switch off of a desktop environment is kind of a non-starter to me. It stinks because I really want to use Wayland, but even as recently as a month ago I tried to see if I could make the switch and couldn't.

Truthfully, if someone has a lot of money to dump around, devoting a few full-time developers or dropping cash on https://github.com/OpenTabletDriver/OpenTabletDriver would probably go a long way towards encouraging Wayland adoption from artists.

As far as I can tell the issue is not that Wayland can't do tablet control on the same level as X11, it's that the tools built around those capabilities still seem immature. OpenTabletDriver looks very promising but seems to have limited device support, limited in no small part by what tablets the devs have access to (my Cintiq 32 is unlikely to get added any time soon because it is no longer being sold and was expensive and uncommon when it was on the market -- which probably means I should try to do it, but it's been tough to find the time).

The NVIDIA situation is also a problem, but there's nothing anyone can do about that other than yell at NVIDIA more.

----

> The text tool is a joke.

The text tool should see considerable improvement soon; the entire text engine got rewritten in the last release, the devs just only had time to get it to feature parity with the existing tools.