![\"Mascote](\"\/wp-content\/uploads\/2026\/09\/wayland-v2.webp\")
<\/p>\n<\/p>\n
In 2017 Wayland was still \u201cthe future.\u201d In 2026 it is the present<\/strong> of the Linux desktop: a compositor instead of the X server, less complexity, better HiDPI and security. This post's title stayed in the past \u2014 the protocol did not.<\/p>\n <\/p>\n Wayland is a protocol (and a C library) for the compositor<\/strong> to communicate with clients. The compositor can be the environment itself (Mutter, KWin, Sway, COSMIC, Weston) running on KMS\/evdev. Clients are native apps, or a rootless<\/em> X server (XWayland) for software that has not migrated yet.<\/p>\n Weston, the reference implementation, still exists for testing and embedded systems. On actual desktops, the desktop environments\u2019 compositors are in charge \u2014 not an \u201cX server\u201d in the middle.<\/p>\n X11 was born in 1987. In 26 years (when Kristian H\u00f8gsberg started Wayland), hardware and UIs had changed: the X server stopped rasterizing \u201crectangle here, text there\u201d and started receiving finished buffers from the toolkit. In the words of Daniel Stone<\/strong> (talk at linux.conf.au 2013), the protocol became \u201ca terrible communication protocol between the client and the window manager\u201d \u2014 with tearing, gray windows before painting, and keyboard grabs that freeze the screensaver.<\/p>\n The X.Org wiki even listed a hypothetical \u201cX12\u201d: what they would do differently if they could redesign the protocol. It was not a serious project; it was a diagnosis. Backward compatibility is X.org policy: four input models, four display models, two rendering models, ~23 active extensions. Every small fix became a disproportionate amount of work.<\/p>\n Wayland itself only exists because X.org cleaned up DRI2, KMS, and Mesa in 2000\u20132010. Stone: \u201cWayland would not be possible without the last few years of X.org development.\u201d.<\/p>\n It starts from scratch, with the modern<\/em> role of the display server: the client draws the buffer, the compositor puts it on screen. A pop-up, for example: in X11 the client requests a global keyboard\/mouse grab; in Wayland the compositor knows what a popup is and closes it automatically if you click outside \u2014 media keys and the screensaver do not stop working along the way.<\/p>\n Old X apps do not need to be rewritten all at once: XWayland<\/strong> is an X server running as a Wayland client. That is how GNOME 50 and Plasma 6.8 still open that GTK2\/Qt5 binary nobody is going to port.<\/p>\n Stone predicted that 2013\u20132014 would be \u201ca very good year\u201d for GNOME and KDE ports. It took longer, but it happened:<\/p>\n Xfce and Cinnamon still carry X11 alongside Wayland. For GNOME\/KDE users on a current distro, the title's question has already been answered at login.<\/p>\n In GDM, the session selector (the gear on the login screen) still exists in releases that offer both. In Ubuntu 26.04 GNOME, the Xorg option disappears from the menu. Tools that depend on X11 did not \u201cdie\u201d overnight: it became a compatibility layer. In 2026, the compositor speaks Wayland.<\/p>","protected":false},"excerpt":{"rendered":" In 2017, Wayland was still \u201cthe future.\u201d In 2026, it is the present of the Linux desktop: a compositor instead of the X server, less complexity, better HiDPI and security. This post\u2019s title stayed in the past \u2014 the protocol did not. \u2026 Read more<\/a><\/p>","protected":false},"author":0,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,97,98],"tags":[4,99,101,100],"class_list":["post-152","post","type-post","status-publish","format-standard","hentry","category-linux","category-wayland","category-x-org","tag-linux","tag-wayland","tag-x","tag-x-org"],"_links":{"self":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/152","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/comments?post=152"}],"version-history":[{"count":5,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/152\/revisions"}],"predecessor-version":[{"id":1151,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/posts\/152\/revisions\/1151"}],"wp:attachment":[{"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/media?parent=152"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/categories?post=152"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.linuxpro.com.br\/en\/wp-json\/wp\/v2\/tags?post=152"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What Wayland is<\/h2>\n
Why X.org could no longer keep up<\/h2>\n
![\"Arquitetura](\"\/wp-content\/uploads\/2026\/09\/mesa-wayland-arch.webp\")
<\/p>\nHow Wayland is different<\/h2>\n
![\"Arquitetura](\"\/wp-content\/uploads\/2026\/09\/wayland-arch.webp\")
<\/p>\nWhat happened from 2017 to 2026<\/h2>\n
\n
How to check (and when to go back to X)<\/h2>\n
echo $XDG_SESSION_TYPE\n# wayland ou x11\n<\/code><\/pre>\nxdotool<\/code>, global grabs, or classic X11 forwarding over SSH remain X's niche \u2014 or require a portal\/PipeWire in place of old-style screen sharing.<\/p>\nReferences<\/h2>\n
\n