Wayland has some good ideas to modernize the stack based on passing GPU buffers between the compositor and applications, so that applications can use GPU acceleration and actual 21st century graphics technology to the fullest. But the non-graphics part of a desktop GUI are hard (e.g. event routing, clipboard, drag and drop, screenshots/capturing...). Wayland suffers from two things in this regard: first, it needs to catch up to a 30 year headstart thatball other DEs have with implememting that. Second, it is artificially hobbling itself by declaring absolutely trivial information privileged like the screen resolution and absolute coordinates of any window on the screen. This is a list of stumbling blocks and showstoppers that have to be worked around.
Re:The death watch for the X Window System has probably started
by noobermin on Sunday July 07, 2019 @05:44PM
(#20378096)
I made a comment on this below, X already exists, why can't people live with X/fix X and thus utilize the already existing code vs recreate all the interfaces that X already has?
[ Parent
| on HN ]
Re:The death watch for the X Window System has probably started
by gmueckl on Sunday July 07, 2019 @06:10PM
(#20378288)
X is a dated mess at this point. Its core architecture assumes a model for drawing graphics that is more than teo decades out of date. There have been extensions - plenty of them - to drag it along and these have added substantial bloat. Also, some extensions where also awfully half-baked, turning the X11 protocol into nightmare to program against.
Re:The death watch for the X Window System has probably started
by kilburn on Sunday July 07, 2019 @06:19PM
(#20378340)
Because X's developers gave up on it: https://www.phoronix.com/scan.php?page=article&item=x_waylan...