Wayland
A next-generation display protocol for Linux desktop graphics, initiated in 2008 by Red Hat engineer Kristian Høgsberg. Its core design principle is 'compositor as server,' offering lower latency, improved security isolation, and a more streamlined architecture compared to X11.
Core Facts
Timeline (last 90 days)
Waydroid is currently the most mainstream solution for running Android applications on Linux phones; it works by running a complete Android image inside a Linux container (LXC) and rendering app output to the Linux desktop by bridging the Wayland display protocol.
In a Wayland environment, traditional X11 tools (such as clipboard scripts based on xdotool) often fail to work properly.
Hyprland is a Wayland-based tiling compositor that handles both window management and screen compositing.
i3 is currently the most popular X11 tiling window manager, and Sway is its spiritual successor under the Wayland compositing protocol, with an API highly compatible with i3.
VoxType captures keystrokes by directly reading /dev/input event devices, bypassing Wayland's input isolation restrictions
Wayland's security model prohibits global input interception, causing most voice input tools to fail under Wayland compositors or require special permissions
Wayland is a next-generation compositor protocol on the Linux desktop that replaces the legacy X11 display protocol and has become the default session environment in mainstream distributions such as Fedora and Ubuntu.
Squint currently supports Windows 10/11 and Linux (Wayland), with no macOS support at this time.
Under Wayland, X11 applications need to run through the XWayland bridge for emulation.
Wayland provides a cleaner scaling solution path by having each application render at the scaling ratio on its own (per-surface scaling), but this requires synchronized support from toolkits such as GTK4 and Qt6.
24 more timeline events
All Facts (20)
GNOME has already defaulted to Wayland, and KDE Plasma also set Wayland as the default in 2024.
75%UnverifiedWayland相比传统的X11协议,在安全隔离和图形渲染效率上有显著优势
85%UnverifiedWayland is a Linux display server protocol designed to replace X11, which has a history of over 30 years, and isolates inter-application input event access at the protocol level.
70%UnverifiedUbuntu has defaulted to Wayland since version 22.04, and Fedora switched to Wayland in version 25.
60%UnverifiedWaydroid is currently the most mainstream solution for running Android applications on Linux phones; it works by running a complete Android image inside a Linux container (LXC) and rendering app output to the Linux desktop by bridging the Wayland display protocol.
50%UnverifiedHyprland is a Wayland-based tiling compositor that handles both window management and screen compositing.
50%UnverifiedIn a Wayland environment, traditional X11 tools (such as clipboard scripts based on xdotool) often fail to work properly.
50%Unverifiedi3 is currently the most popular X11 tiling window manager, and Sway is its spiritual successor under the Wayland compositing protocol, with an API highly compatible with i3.
50%UnverifiedWayland's security model prohibits global input interception, causing most voice input tools to fail under Wayland compositors or require special permissions
50%UnverifiedVoxType captures keystrokes by directly reading /dev/input event devices, bypassing Wayland's input isolation restrictions
50%UnverifiedWayland is a next-generation compositor protocol on the Linux desktop that replaces the legacy X11 display protocol and has become the default session environment in mainstream distributions such as Fedora and Ubuntu.
50%UnverifiedSquint currently supports Windows 10/11 and Linux (Wayland), with no macOS support at this time.
50%UnverifiedWayland provides a cleaner scaling solution path by having each application render at the scaling ratio on its own (per-surface scaling), but this requires synchronized support from toolkits such as GTK4 and Qt6.
50%UnverifiedWayland is an X11 replacement project launched in 2008 that uses the compositor directly as the display server.
50%UnverifiedUnder Wayland, X11 applications need to run through the XWayland bridge for emulation.
50%UnverifiedUnder Wayland, scenarios such as screen sharing and accessibility are gradually being filled in through PipeWire and the portal mechanism.
50%UnverifiedWayland's security model is stricter than X11's; applications cannot arbitrarily listen to keyboard events from other windows or directly manipulate the clipboard, and must instead use dedicated protocols such as zwlr_data_control or xdg-desktop-portal.
50%UnverifiedOpenWhispr has poor support in Wayland environments; basic dictation works out of the box, but assistant mode and hotkeys barely function properly.
50%UnverifiedUnder Wayland, clipboard access typically requires the window to be in focus or to be arbitrated by the compositor, preventing applications from freely polling clipboard content in the background.
50%UnverifiedMany applications run through the XWayland compatibility layer, which reintroduces some of X11's security weaknesses to a certain extent.
50%