Hacker News new | ask | show | jobs
by Chu4eeno 11 days ago
One of the issues with Wayland is that it forces every compositor to reimplement the X server, badly.

So you can't really "fix it", short of patching e. g. Gnome's compositor, with patches that will never be accepted upstream.

1 comments

It's also an 80% solution, the same thing so many rust "rewrites" are notorious for. Sure it finally mostly works at this point. Mostly. But it took a decade of kicking and screaming to get here and there are still edge cases that don't work, many clearly viewed as wontfix simply because there isn't enough popular support to force the hand of the purists. Hopefully llms make a community bootleg wayland protocol effort viable.
That's a bit dishonest since you're forgetting about all those features that now work, aren't you?
Not at all. "Sure it finally mostly works at this point. Mostly." I explicitly acknowledged that after 10+ years of needless drama something like 95% (handwave) of the extended feature list is working.

And so much of it really was needless drama. Go read through many of the wayland protocol extension issue tracker threads. The amount of intentional heel dragging, willful ignorance, and purity spiraling is off the charts (IMO obviously).

To be clear I like and use wayland in its current state. There are plenty of valid criticisms of X11. IMO a redo was not a bad idea per se and it eventually turned out well enough (provided your app doesn't depend on the 5% that suffers an arbitrary rejection).