None of the issues I’ve had with X (drivers, mostly) will be resolved with Wayland. For me, it’s a solution in search of a problem.
You’re welcome to continue to develop and maintain X, wrapping even more duct tape around all that duct tape, noone is stopping you. Or, alternatively, you simply never had a look at the X source code – I cannot fathom a developer who would be masochistic enough to actually maintain that codebase. It was unsalvageable when the devs started to abandon it for Wayland, fifteen years ago, it’s not any more salvageable now.
And if you want to “Fix X” – that, precisely, is wayland: X is a buggy mess of fundamentally insecure software, developed before “buffer overflow” was a thing people acknowledged as security issue. It’s software from the age of strlen. It cannot be fixed while keeping it compatible and if you have used X “since the 90s” you know very well how much of a shitshow it is, and it does not just “pop things up on your screen and lets you interact with them”. Random thing: In wayland, programs can’t focus fight.
I’ll move to Wayland when I have to, but right now there’s no reason to not use X.
Yes, there is: Making the transition faster. All this griping people are doing right now and during the last what five years could’ve been avoided if DEs, window managers, toolkits, etc, had actually paid attention to what the X devs were doing. All those screen sharing and global shortcut protocols could have been ready ten years ago.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
You’re welcome to continue to develop and maintain X, wrapping even more duct tape around all that duct tape, noone is stopping you. Or, alternatively, you simply never had a look at the X source code – I cannot fathom a developer who would be masochistic enough to actually maintain that codebase. It was unsalvageable when the devs started to abandon it for Wayland, fifteen years ago, it’s not any more salvageable now.
And if you want to “Fix X” – that, precisely, is wayland: X is a buggy mess of fundamentally insecure software, developed before “buffer overflow” was a thing people acknowledged as security issue. It’s software from the age of
strlen. It cannot be fixed while keeping it compatible and if you have used X “since the 90s” you know very well how much of a shitshow it is, and it does not just “pop things up on your screen and lets you interact with them”. Random thing: In wayland, programs can’t focus fight.Yes, there is: Making the transition faster. All this griping people are doing right now and during the last what five years could’ve been avoided if DEs, window managers, toolkits, etc, had actually paid attention to what the X devs were doing. All those screen sharing and global shortcut protocols could have been ready ten years ago.
Why do I care about the state of the code? It works. Perhaps all these people complaining are really just sick of your proselytization.
To paraphrase Terry Pratchett, “You only get one life. You can pick up five causes on any street corner.”