Wayland is a protocol, not a desktop environment. It describes how clients and a compositor communicate. A compositor is the program that manages surfaces, receives input, and presents the composed result. GNOME Shell, KDE’s KWin, Sway, and Hyprland are different desktop/compositor experiences built around this broader model.
The distinction matters because X11 often let applications make assumptions about a shared global desktop: where windows were, how to inspect other windows, or how to observe input. Wayland’s model is more explicit. A client communicates with the compositor through protocol objects and requests; the compositor mediates what becomes visible and how input is routed. The Wayland documentation describes the protocol as asynchronous and object-oriented, while the architecture guide follows events from input devices through the compositor to clients.
This changes customization. A shell extension, screen recorder, global hotkey utility or automation script may need a compositor-specific protocol or portal instead of relying on an old global API. Portals provide a user-mediated interface for tasks such as screen capture and file selection. The resulting friction is not accidental in every case: isolation is part of the design, though incomplete or inconsistent protocols can still make a workflow awkward.
It also changes where a desktop’s personality lives. In a tiling compositor, window placement and keyboard workflow are often configured close to the compositor. In a full desktop environment, panel, launcher, settings and accessibility facilities may arrive as a more integrated system. Neither is inherently more “real” Linux. The useful question is how much of the environment should be explicit configuration and how much should be supplied as a cohesive default.
Wayland is not one uniform implementation. Protocol extensions vary, compositors differ, and applications still have compatibility constraints. A careful setup guide should name the compositor and relevant versions rather than saying simply “Wayland supports this.”
The VOID//SIGNAL desktop borrows the visual grammar of a compositor—workspaces, focus, windows—without claiming to emulate one. That is the interesting design lesson: an interface can borrow a workflow’s clarity without pretending to be the underlying system.
Sources: Wayland protocol model, architecture, and project overview.