A switch from X11 to Wayland is not just a minor change to your workflow though unless you used all defaults before.
It requires you to replace your window manager, all the little tools related to things like clipboard, automation, screen locking,…
And you would have to do pretty much all of that up front to be able to use Wayland long enough to know if it even works on a permanent basis for you. That is a lot of work to put into a project that has a sketchy history of people claiming for nearly a decade now that it works just fine for everything while clearly not working fine for all use cases.
I suppose it’s more difficult if your desktop environment doesn’t support Wayland, so you’d have to replace it entirely. I can imagine that’s a pain, but that’s not exactly the typical use case.
Luckily, I doubt X.org will be abandoned any time soon, so the minority stuck in their old X.org exclusive environments will be able to use their programs unchanged for years to come. Eventually X.org users will be in the same position Wayland users were in years ago (having to apply workarounds for missing APIs to keep everything running smoothly) but I doubt that’ll happen soon.
Clipboards work out of the box in the Wayland compositors I’ve used (Gnome, KDE, Deck UI), as does screen locking. Most automation also works, at least between X11 applications running under XWayland, but that’s the “workflow” thing I mentioned; xdotool needs to be replaced by ydotool and maybe some DBus calls, depending on your setup, but a few aliases and an afternoon of work should work around those problems when the time to switch eventually comes.
I believe xsel and xclip can be replaced pretty easily with wl-clipboard or one of the alternatives for that.
I don’t use multi-clipboards myself, so I couldn’t tell you what to use as an alternative. I think CopyQ supports Wayland? Or maybe you need to cook something up with one of the Wayland <-> X11 clipboard sync tools.
The point wasn’t so much that there are no replacements, more that every script and every shortcut and everything else using them will have to be changed to work with the Wayland alternative.
A switch from X11 to Wayland is not just a minor change to your workflow though unless you used all defaults before.
It requires you to replace your window manager, all the little tools related to things like clipboard, automation, screen locking,…
And you would have to do pretty much all of that up front to be able to use Wayland long enough to know if it even works on a permanent basis for you. That is a lot of work to put into a project that has a sketchy history of people claiming for nearly a decade now that it works just fine for everything while clearly not working fine for all use cases.
I suppose it’s more difficult if your desktop environment doesn’t support Wayland, so you’d have to replace it entirely. I can imagine that’s a pain, but that’s not exactly the typical use case.
Luckily, I doubt X.org will be abandoned any time soon, so the minority stuck in their old X.org exclusive environments will be able to use their programs unchanged for years to come. Eventually X.org users will be in the same position Wayland users were in years ago (having to apply workarounds for missing APIs to keep everything running smoothly) but I doubt that’ll happen soon.
Clipboards work out of the box in the Wayland compositors I’ve used (Gnome, KDE, Deck UI), as does screen locking. Most automation also works, at least between X11 applications running under XWayland, but that’s the “workflow” thing I mentioned;
xdotoolneeds to be replaced byydotooland maybe some DBus calls, depending on your setup, but a few aliases and an afternoon of work should work around those problems when the time to switch eventually comes.I was talking about tools like xsel or xclip or clipboard managers for multiple clipboards.
I believe
xselandxclipcan be replaced pretty easily withwl-clipboardor one of the alternatives for that.I don’t use multi-clipboards myself, so I couldn’t tell you what to use as an alternative. I think CopyQ supports Wayland? Or maybe you need to cook something up with one of the Wayland <-> X11 clipboard sync tools.
The point wasn’t so much that there are no replacements, more that every script and every shortcut and everything else using them will have to be changed to work with the Wayland alternative.
You use requires but those are not requirements. It applies to some cases.
Sketchy history? Seems biased.