story
When Wayland will get better and apps start supporting Wayland more than they support X11, it will be the time to switch, but at the glacial pace Wayland advances, chances are that your current system will be obsolete when it will happen.
It is still a good idea to consider Wayland support for your own apps and have at least a test machine running it, but doesn't mean writing apps designed to work with X11 like this one is a wasted effort. X11 is here to stay, for a while at least.
Occasionally, I've enjoying playing around with window management and hacking with WMs, using stuff like this and/or xdotool and wmctrl.
I was curious as to what this might be like in Wayland-land? Do tools like this even exist?
There is no way to do the equivalent of xdotool type --window 0x600005 "my important input"
Ydotool readme:
> Currently implemented command(s):
> type - Type a string
> key - Press keys
> mousemove - Move mouse pointer to absolute position
> click - Click on mouse buttons
So... No.
It's pretty clear. But some are too stuck up to even research it or be part of shaping it. Which is common among legacy vendors who very rarely even care to communicate with Wayland developers about their needs.
Those who aren't stuck up deal with it just fine (OBS Studio for example).
If you run more than one monitor with different DPI, Wayland is the only choice. If you want to do HDR, Wayland will be the only choice.
> When Wayland will get better and apps start supporting Wayland more than they support X11, it will be the time to switch, but at the glacial pace Wayland advances, chances are that your current system will be obsolete when it will happen.
Toolkit developers are already considering removing their X11 code paths. All of the effort is going into Wayland. The best time to switch was a few years ago. The second best time to switch is now.
For me it's definitely not usable yet, let alone the "only choice"
> All of the effort is going into Wayland
Yes, because it's still work in progress. And at some point in the future that effort will have paid off, but that's not now and definitely not a few years ago.
And because the X11 maintainers decided that Wayland is the way forward and X11 will simply not get new display features like HDR.
Is Wayland a racket? Barely maintain the previous code instead of making clear that others should take it over because you are insterested in something else, then force everyone into your new incomplete code base, and probably bill for the reimplementation of basic capabilities, piece by piece.
OTOH, not everyone involved with X11 thinks it has no future. Keith Packard posted ideas [0] about how to improve it further.
I run multiple monitors with differing physical DPIs on X11. Yeah, that means they have differing resolutions. It doesn’t bother me, and I can do all the things that I want, unlike if I were using Wayland.
Maybe someday Wayland will be a replacement for X11, but that day is not today.
I'd say within this year already. Some major parts like explicit sync are being merged already. And all future work (like HDR) will only go to Wayland. Not to X11.
So this claim that X11 is a viable option is a fallacy.
It's my computer. I decide what's "the way to go" or "viable" there. None of your business. No one is forcing you or anyone to use it.
This is clearly a "I wrote it because it's useful for me, I put it online for whom it may concern"-type of project. You need to calm your tits and stop shitting all over people's hobby projects.
