[slowbdotro]

If you wanted, you honestly could stay on X11 for the next decade. I highly doubt it's going anywhere. Also, no matter what your workflow is, you can write a program to do that. I'd guarantee you could write a small script to automate Wayland to do what you need

[kamov]

Right about now KDE is moving to Wayland. KDE Plasma 6 released a week ago will use Wayland by default, with X11 being an opt in mode. I think that X11 while it might exist for the next decade, it will at best be a second class citizen, at worst a buggy and unsupported mess

[oliwarner]

And even if they pull X support, do you have to use Plasma 6, 7 or 8 in the next decade?

Sometimes it's okay to use old software, especially if it works well for you.

[roenxi]

Is it technically possible to guarantee program-agnostic mouse gesture support in Wayland? I would sorta expect wlroots to support it, but I don't think that is a safe bet for an arbitrary Wayland compositor.

[qwertox]

This is my main issue, I need full access to input devices and the ability to drop, alter and inject new events.

On Windows I fully rely on StrokeIt, it has been a huge improvement for me which I've used for ~15 years.

Linux's easystroke [0] is now deprecated (and always was mediocre) and the modern alternative "mouse-actions" [1] is not good at all.

I've coded a replacement in Rust+C which works for my simple use-case but it targets X11 and it's unclear for me how I can get low level access to input devices events with Wayland. I've also read something about security getting increased in Wayland so that one does no longer have access to input stuff (unclear to me).

Then the nice thing about X11 is the ability to remotely use a X11 session, which apparently isn't possible with Wayland (except for RDP or VNC which isn't what I need).

[0] https://github.com/thjaeger/easystroke/wiki

[1] https://github.com/jersou/mouse-actions