What else is being worked on currently to replace the very aging x11?
If it’s x11. . . The devs have basically said it would need a complete rewrite since it’s got so much code and patches and what not over the years, and currently they aren’t really working on it. So if it’s still x11 when does the renaissance of it start?
The reality is that the FOSS community and Linux community often take part in flamewars and gate-keeping.
I mean… even baby-Linux itself was part of one of the most popular flamewars ever !
What I’d say is objective, is that you’re a winner for leaving Windows behind.
At the end of the day Linux is what allows you to have all those choices to argue for or against!
I say, just use whatever fits your needs and works best for you.
Other people’s opinions on YOUR system are completely irrelevant.
Of course (let me be clear) oftentimes arguments for both positions of a debate can be made, discussed and result in a productive (or sometimes not…) outcome. So in my opinion exposing yourself in different opinions is great (essential even) regardless.
Just as an example of the things you mentioned, some people hate systemd-boot (and systemd in general) with passion…
And some of the arguments against it do make sense (eg I don’t like binary logs either).
That said, for me personally, in over a decade of using Linux, grub was the only thing that ever (repeatedly!) borked my system.
So I moved to systemd and forgot about it.
I have absolutely no need to argue for or against it.
There’s tons of arguments on the matter already floating around the internet sea, people can read those and decide for themselves.
But just think of how much fossil fuels you can save if the WHOLE world just went to sleep vs showing sexy screensavers?
Yeah, that’d be a lot sleeping…
Everyone who is suggesting ydotool as a replacement for xdotool doesn’t know what they are talking about. Of course I’ve considered that, that’s the first result in any search engine, when one looks up “xdotool on Wayland”!
Just like Wayland itself, ydotool is woefully inadequate. It is not only inherently unsafe (talk about Wayland being an improvement in security, ha ha, good joke!), it lacks the most basic features of xdotool.
Also, why is security suddenly important? You said you would be okay with it if you as a user can choose. You need to start a service and add your user to the input group.
The real question is, can you do your tasks with ydotool? And if not, why not?
It always was, I never said that it wasn’t. I’m just not deluding myself into thinking that Wayland offers me any additional security. Well, that’s not enirely correct, it offers me additional security in the same way as keeping my computer offline does, that is, by removing essential functionality. Just because I find that unacceptable and unreasonable shouldn’t make you think that I ignore the separation of privileges and other common-sense security practices in a cavalier way. I shouldn’t be needing root access to make an auto-clicker.
Is that (*not being able to capture keys on wayland) still the case?
I thought I’ve read that some work had been done to “whitelist” specific applications listening to specific keys.
Also, Xeyes is a prime example of that not working (not for keystrokes but for mouse coordinates, but the principle is the same).
I like Xeyes, it’s not just a funny gimmick but an actually useful tool for someone like me who has poor eyesight and has trouble finding the mouse cursor on the two huge monitors. Yes, there are other ways of locating the mouse cursor, but they are all soulless and boring.
I like so many things about X that just don’t work on Wayland. I love GUI automation, I love programming “smart” programs that figure out on their own where to click. I like when my program types text into another program. I like to keep a terminal open at all time, and issue key shortcuts that type many commands into that terminal window, the program has to be able detect it and not type in a wrong window. It also needs to know whether there is a program other than shell running in that terminal. There are so many little details to consider.
Yes, there are workaround with Wayland for some of those things, but they all suck. They lack elegance, simplicity, and are inherently not secure.
Oh come on guys, it’s fairly clear that whatever you do won’t like wayland.
Even if Wayland would actually do all the things that needs to do - ain’t gonna like it.
Mainly because of the problem with it’s ideology, it’s bulletproof argument about how it works with programs…It requires rewriting literally ALL software ever created in order to some day drop xwayland - ain’t gonna happen. So ain’t gonna like it therefore.
I don’t think that’s gonna happen… Wasn’t that pretty much the reason it wasn’t named X12 (the work on Wayland was by the same devs to my knowledge and intended as a re-write leaving “obsolete” functionality behind)?
That said, I understand that your needs are not met by it and it kinda sucks for you.
The best suggestion I could make is to do your best to contribute either what’s missing on wayland, or maintenance work on X (which would be absolute hell judging by the people who built it abandoning it ).
I don’t see any other way the future suiting your needs…
@keybreak: here is a short list of things I would want in a Wayland compositor:
Ability to listen to keypresses and get mouse coordinates in any window, focused or unfocused.
Ability to see the pixel contents of any window canvas, from any running process.
Ability to detect all windows, their coordinates, their names and titles, and have a unique ID associated with every one of them.
Ability to issue commands from an external application to show, hide, close, minimise, maximise, etc… any window.
Ability to simulate keypresses, mouse movement and clicking from a user process, without needing privilege escalation.
A gap between monitors in a multi-monitor setup.
Ability to have fully transparent, borderless windows.
If I could have that, I would be happy using Wayland.
This is out of the question from the start, because I don’t have the willpower to write proposals and engage in politics and lobbying. If it were only up to me, and required some coding, I’d do it, but convincing a bunch of morons on the wayland committee to adopt my ideas into their protocol, forget about it.
X is not going anywhere for the foreseeable future.
I think … what currently happens is that Major Desktop and Distro Development try to force Wayland to force completion.
May for the good… as developments main enemy is development time. Developing for both Xorg and Wayland is more work and is causing a lot of time i bet.