Red Hat Enterprise Linux 10 Plans for Wayland and Xorg Server

Original Article ↗ Hacker News Discussion ↗

Red Hat plans to ship RHEL 10 without the Xorg display server, relying instead on Wayland plus Xwayland compatibility, prompting debate over stability versus modernization in a long-term support enterprise distro. Supporters argue X11 is effectively legacy, hard to maintain, and holding back work on a cleaner, more secure graphics stack, while critics say Wayland still lacks feature parity for many real-world workflows, from custom window managers and remote desktops to certain accessibility and input-capture use cases. Many see parallels to the systemd transition, with concerns about corporate influence, shrinking user choice, and the cost of repeatedly reworking setups that have “just worked” for years.

Red Hat’s Decision and LTS Rationale

  • RHEL 10 (around 2025) will drop the Xorg server and other X servers, keeping only Xwayland.
  • Many commenters argue this fits Red Hat’s long‑term support model: if X stayed in RHEL 10, they’d be de facto supporting it to ~2035; dropping it now sets a clear deadline.
  • Others see this as contrary to RHEL’s “stability” branding and as forcing migration before Wayland reaches full feature parity.
  • Several point out that RHEL 9, which still has Xorg, is supported until 2032, giving roughly a decade of overlap.

Wayland Maturity vs. Xorg

  • Pro‑Wayland side:
    • Xorg is old, architecturally problematic, and effectively in minimal‑maintenance mode.
    • Many original X developers themselves chose to build Wayland; they believe only Wayland has a future.
    • Security, multi‑DPI, HDR, newer input/output models, and long‑term maintainability favor Wayland.
  • Skeptical side:
    • Wayland is described as “half‑baked” after a decade+, with important protocols stuck in review and fragmentation across compositors.
    • Some desktop environments and tools (e.g., panels, embedded compositors, advanced menus/pie menus, custom WMs, scripting around window management) can’t yet be ported cleanly without private protocols or major rewrites.
    • Remote desktop, VNC/X forwarding–style workflows, and some accessibility or overlay tools are still weaker or more complex.

Xorg, Xwayland, and Legacy Apps

  • Xwayland is expected to handle most X11 apps, reducing impact for typical RHEL customers who mainly use GNOME/KDE and toolkit‑based software.
  • Concern remains for niche and power‑user setups: custom window managers, heavily scripted X11 environments, X11 network transparency, and certain gaming/driver combinations (especially some Nvidia cases).
  • Some suggest Xorg can live on outside RHEL, or via Xwayland indefinitely; others think Xwayland will eventually be dropped too, though this is not stated as a concrete plan.

Governance, Red Hat, and Systemd Parallels

  • Multiple commenters compare this to the systemd transition:
    • A vocal minority objects; most users “just use it”.
    • Red Hat is seen as steering core infrastructure (init, display stack) toward its preferred designs, with critics feeling choice is eroded.
  • Counter‑argument: in open source, whoever does the work decides; if no one is willing to seriously fund/develop Xorg, it is natural for it to be phased out.

Security vs. Flexibility

  • Wayland’s tighter security (no global keylogging, global grabs, arbitrary screen capture, or client‑side window management) is praised as necessary, especially as Linux gets more app‑store‑like.
  • Others argue the restrictions broke many legitimate workflows and tools; they would prefer opt‑in permissions or portal‑style dialogs without losing X11‑level flexibility.