Make amazing things that can’t be replicated on X. Notably the list of things people think only works on Wayland is long and wrong. Right now there is a vibrant window manager ecosystem and HDR.
Alternatively wait until new versions of basic apps no longer work on X. Although it would be hilarious if we got a comparability layer to run wayland apps on x
Unless there’s a replacement without losing functionality, it’s going to be hard. I waited years for the switch to let wayland be ready. I thought it was when kde defaulted to Wayland, but nope. Once every month I run into issues related to Wayland. Or I run into not being able to implement certain things in Wayland that were super easy in x11.
I mean yes we could force the transition, but for many people maintaining their workflow and features are important. That said, I would want new applicationd snd libraries to support Wayland.
I switched from autokey to espanso when kde/Wayland forced me to abandon X, I gotta say I really like espanso now. I also use ydotool and it seems fine. I’m writing a kde-specific puautogui replacement right now.
X11 really needs to be put down. Its had its time
Make amazing things that can’t be replicated on X. Notably the list of things people think only works on Wayland is long and wrong. Right now there is a vibrant window manager ecosystem and HDR.
Alternatively wait until new versions of basic apps no longer work on X. Although it would be hilarious if we got a comparability layer to run wayland apps on x
Unless there’s a replacement without losing functionality, it’s going to be hard. I waited years for the switch to let wayland be ready. I thought it was when kde defaulted to Wayland, but nope. Once every month I run into issues related to Wayland. Or I run into not being able to implement certain things in Wayland that were super easy in x11.
I mean yes we could force the transition, but for many people maintaining their workflow and features are important. That said, I would want new applicationd snd libraries to support Wayland.
Just give it another 10 years and a few hundred thousand dollars of budget and it’ll be finally good (it won’t)
I can’t get by without xdotool. Wayland intentionally breaks this and calls it security.
What deficiencies does ydotool have for your workflow?
It’s abandoned it’s GitHub page talks about rewriting in JavaScript in 2024. X actually gets security updates.
Sending keys to non-active windows without activating them.
It looks like ydotool also needs root, and has weird interactions with non-qwerty keyboard layouts.
I’ve also been using Autokey lately which has similar blockers with Wayland.
I switched from autokey to espanso when kde/Wayland forced me to abandon X, I gotta say I really like espanso now. I also use ydotool and it seems fine. I’m writing a kde-specific puautogui replacement right now.
I’m in the same boat. Looks like there is a whole bunch of alternatives: https://superuser.com/questions/1032270/wayland-alternative-for-xorgs-xdotool
The seem to have their own issues, which isn’t great, but so does xdotool.