If u wanna use drawing tablets, you’re better off sticking with X.
Wayland has support for drawing tablets, it (libinput specifically) even has good support for drawing tablets, they just cannot in any way, shape or form be configured on wayland, or if they can be, then nobody knows how to do it, so practically speaking they can’t be.
You lose nothing of importance by moving from wayland to x usually, the only thing I can think of that you might feasibly end up in trouble with is that wayland has slightly better multi-monitor support than X. That’s it. That’s the only thing I can think of that wayland does better than X, it really isn’t worth any of the hype that’s being tossed at it.
I was playing around with kmonid and keyd to achieve similar functionality but none were really what I was used to. I guess i need to possibly step down and accept it’s not as easy to make it work
i guess yeah. i probably need to switch to X. I started on wayland 2 days ago and logged into x once but i coould feel it was not as smooth as wayland tho. But most likely due to issues of mishandling pacman haha
i think the latest kde update made it possible to adjust the pressure sensitivity, not a 100% on that, could be it’s not on wayland (saw in a phoronix article today) but if you need more than that, then yeah, go for X.
There shouldn’t really be a difference in performance between X and Wayland, Wayland just sometimes feels smoother cuz vsync is always forced on on wayland. Has been since the start, it was supposed to be one of their main selling points, and in a way it was because getting vsync to work on X (as in for the window manager and compositor, generally not in games) was sometimes kinda messy, and X without vsync tends to have pretty bad tearing problems on some gpus.
But it is a feature that hasn’t really aged well (gamers in particular hate it, because turning off vsync is sometimes good for games)