That’s a meaningless statement. You can kill any process at any time. The point is do you notice as a user what that process does?
It’s implemented right now. I want to share my screen? You have to sudo something or the DE asks me.
You want Xeyes forever fine, stay with Xorg. But you have to understand that others don’t perceive it as “broken” but a “feature”, even if you personally disagree. There’s a reason why people actually working on all the different parts in the software stack decided to go down that road instead of the old model.
Was I happy to inject code into the running kernel/programs twenty years ago? Sure. It allowed great features. Do I think that’s a good idea today? No. - Same line of reasoning. Times have changed.
Yes, as a user, you are responsible for what each process does.
And no, basic features shouldn’t require privilege escalation. There is a reason privileges are separated. This merely encourages reckless use of sudo and therefore actually lowers the security of the system.
That means nothing. The average person is wrong on so many things.
Great, and now we are dragging down the competency level for every user from “reading and understanding the source code” to “you will be asked by the system through a fancy UI dialog”.
Except we are not talking about the average user but the most knowledgeable people about this subject on the planet: the people who were previously in charge of Xorg and working on its successor now.
I agree with Kresimir to a point. Wayland was not designed as a drop-in replacement for X.org and hence broke userspace. Consequently developers were forced to completely re-engineer their applications to support Wayland. However, that’s almost ancient history at this point. The standard going forward is Wayland and I suspect that with time fewer and fewer applications will support X.org. There is no point into getting heated debates about what is fait accompli.
Age is not exactly relevant - how old is X.org? Most major distributions package Wayland as the default display server now. It is in all important respects the new standard and X.org is considered to be legacy software which will continue to be supported in the interim, but eventually will be deprecated. Nobody is developing new features for X.org now and as such it is a question of when not if Wayland will become the standard.
I really disagree with how Wayland was shoved down everyone’s throats with an attitude that smacked a little too much of “Wayland is not broken- Gnome/KDE/[insert popular software application here] is.” But that’s pretty much ancient history now. Wayland has achieved sufficient critical mass now that those arguments are irrelevant.
