lemmyvore, 1 year ago (edited 1 year ago)

I remember reading through that thread when it came out and those are extremely worrying points. Wayland has extremely deep core issues. #2 there alone is horrible.

There are and were alarm bells ringing all around btw with Wayland. From a software developing perspective the approach is terrible. You cannot solve super complex problems by throwing away 30 years worth of code and redoing everything from scratch. You’ll just run into the exact same issues again. Which no, haven’t gone away as the technology advanced as many people would like to believe, we’re still using displays and networking and keyboards and mice.

There is a lot of legacy in X but there’s also a lot of accumulated experience and battle-hardened code. The obvious path would have been to keep the good and remove the bad.

Wayland will eventually since those issues but it will take just as long as it took X, because that’s what happens when you start everything from scratch again.

This is filling me with deja vu because it’s exactly what some of us went through with X, trying to piece together a working desktop out of dozens of pieces. But when you point that out you get “ha ha grandpa that’s old stuff, this new stuff won’t have that problem because [insert magic here]!”

Keep in mind that when Wayland started it was supposed to be a mini-server, to be used for the login screen only. Then the idea came to make it usable for stable, controlled and simple devices where there isn’t a lot of user configuration or hardware variation.

How it got from there to “let’s use it for everything on the Linux desktop and ditch X” I’ll never understand.