一份关于将 Xorg 现代化为纯协议图形层的提案
3 分•作者: powerwordtree•6 个月前
Linux 桌面已经花费了十多年时间向新的图形栈过渡。Wayland 带来了许多优势，尤其是在移动风格的安全性与简洁性方面。但在这一过程中，我们正在悄然失去一些宝贵的东西：曾经让 Linux 图形模型独一无二的分布式、协议驱动、传输无关的理念。
这并非怀旧。这些能力对于远程工作、自动化、多机工作流程、瘦客户端、云桌面以及未来的分布式系统至关重要。它们不是“遗留功能”；它们是可能再次变得重要的架构优势。
问题不在于 Wayland 本身，而在于它从未被设计用来支持这些用例。它的设计理念是有意为本地、单用户和合成器中心。这对于移动设备来说是完全有效的，但它为桌面和分布式环境留下了一个空白。
另一方面，Xorg 遭受的是老化的实现，而不是过时的理念。它的核心思想——基于协议的渲染、远程执行、可组合性和传输独立性——仍然具有相关性。我们所缺乏的是一个现代、极简、仅协议的继任者，它在不背负 Xorg 历史包袱的情况下保留了这些优势。
这样的项目不需要复制 Xorg 的整个功能集。它不需要服务器端渲染、字体、输入法、窗口管理或安全策略。它只需要定义一个干净、现代的协议和一个稳定的抽象层。现有的合成器可以实现它。现有的驱动程序不需要更改。Mesa 也不需要进行重大重新设计。工程量远小于重写整个图形栈。
这并非呼吁取代 Wayland。这是呼吁承认 Linux 桌面可能需要不止一个图形模型。一个协议优先、实现无关的层可以与 Wayland 共存，补充它，并保留那些否则将会消失的功能。
如果没人开始这项工作，行业将自然而然地趋向于移动风格的图形架构，而过去的分布式能力可能会被长期遗忘。但如果有人开始一个现代的、仅协议的 Xorg 继任者，社区最终可能会找到一条在简洁性与桌面曾经拥有的——并且可能再次需要的灵活性之间取得平衡的道路。
查看原文
The Linux desktop has spent more than a decade transitioning toward a new graphics stack. Wayland brings many advantages, especially for mobile-style security and simplicity. But in this process, we are quietly losing something valuable: the distributed, protocol‑driven, transport‑agnostic ideas that once made the Linux graphics model unique.<p>This is not nostalgia. These capabilities matter for remote work, automation, multi‑machine workflows, thin clients, cloud desktops, and future distributed systems. They are not “legacy features”; they are architectural strengths that may become important again.<p>The problem is not Wayland itself, but the fact that it was never designed to support these use cases. Its philosophy is intentionally local, single‑user, and compositor‑centric. That is perfectly valid for mobile devices, but it leaves a gap for desktop and distributed environments.<p>Xorg, on the other hand, suffers from an aging implementation, not an outdated philosophy. Its core ideas—protocol‑based rendering, remote execution, composability, and transport independence—remain relevant. What we lack is a modern, minimal, protocol‑only successor that preserves these strengths without carrying Xorg’s historical baggage.<p>Such a project would not need to replicate Xorg’s entire feature set. It would not need server‑side rendering, fonts, input methods, window management, or security policy. It would simply define a clean, modern protocol and a stable abstraction layer. Existing compositors could implement it. Existing drivers would not need to change. Mesa would not need major redesign. The engineering effort is far smaller than rewriting a full graphics stack.<p>This is not a call to replace Wayland. It is a call to acknowledge that the Linux desktop may need more than one graphics model. A protocol‑first, implementation‑agnostic layer could coexist with Wayland, complement it, and preserve capabilities that would otherwise disappear.<p>If no one starts this work, the industry will naturally converge on mobile‑style graphics architectures, and the distributed capabilities of the past may be forgotten for a long time. But if someone begins a modern protocol‑only successor to Xorg, the community may finally have a path that balances simplicity with the flexibility the desktop once had—and may need again.