It wasn't forgotten about - Wayland explicitly chose not to put any control plane into the core, because part of what has not aged at all well in X11 is the assumptions made by the control plane.
Instead, the expectation is that if there's a common control plane that makes sense for today's compositors, and that should be part of the Wayland protocol, compositors will get together and put up a common Wayland extension for that control plane. And then, because it's an extension, if the world changes underneath us such that the control plane is wrong, support for that extension can be dropped.
Remember that a big part of the X11 lesson (as compared to previous iterations of the X Window System) is that protocol extensions are what give you longevity - as a matter of practicality, people are very happy to agree that you need to implement more than just the core protocol to get an acceptable system (e.g. XKB, and MIT-SHM are pretty much required on modern desktops, and some applications require XInputExtension if you want decent support for drawing tablets), so the more that can be moved out of core, the better - nobody remembers PHIGS any more, and because the X11 support for PHIGS was an extension, it just doesn't get implemented.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。