Skip to content
0:00 / 0:00

#wayland#x11#xorg

[Linux.conf.au 2013] - The real story behind Wayland and X

HackersOnBoard

71K subscribers • 11 videos on Hallway

YouTube
  • Recommended by 2 people: 2 on Hacker News.

Intermediate. Assumes working knowledge.

34K views13 years ago2 recommendations

Systems programmingGraphics and audioOperating systemsLinuxRendering

A Wayland developer explains the history of the X Window System and why Wayland was designed to replace it.

The uploader added no description.

Why it's here

2 people recommend this

What people say. Highly recommended for understanding why Linux is transitioning from X11 to Wayland and the architectural flaws of X.

tux1968on Hacker News • Recommends

On “Guide: Full Wayland Setup for Linux”

I tried to give a hint about the basic reason of trying to get out from under the weight of a huge code base that had become old and crufty while the very architecture it was designed around was becoming moot since things were shifting to client side rendering already. Couldn't find a good article on short notice, but there's a decent video from back in 2013 about it. link to this video

kaba0on Hacker News • Recommends

On “Guide: Full Wayland Setup for Linux”

Here you are: link to this video It’s a great presentation by one of the guys behind wayland, who worked on X a lot before. Basically, X has a fundamentally misaligned abstraction of the underlying hardware - which is expected based on its age. When used with a compositor, it is basically a middle-man with no function whatsoever. So Wayland decided to cut out the middle man and pass events directly between client and compositor. But please watch the video, I think it will answer all your questions. Also, it’s not like X will be totally deprecated, XWayland is an API implementation of it that will be supported forever.

kaba0on Hacker News • Recommends

On “Less Than 10% of Firefox Users on Linux Are Running Wayland”

Please have a look at an X maintainers very own presentation: link to this video Wayland is not a middle man as it is the compositor itself as well - it does the minimal amount of work necessary to compose the desktop. X on the other hand just transfers messages between clients and the compositor without doing any actual work (x render functions are almost never used by modern applications)

cypharon Hacker News • Mentions

On “Fedora 25: With Wayland, Linux has never been easier (or more handsome)”

> However it's the lack of network transparency which stops me from using Wayland in the foreseeable future. X is not network transparent, and hasn't been for a long time. link to this video

cypharon Hacker News • Mentions

On “Are We Wayland Yet?”

One of the arguments made by the Wayland spec folks (many of whom were involved in Xorg development for many years) is that the Xorg spec is also a major cause of problems with modern Linux graphics1. 1: link to this video

dralleyon Hacker News • Mentions

On “Red Hat Enterprise Linux 10 Plans for Wayland and Xorg Server”

Here's a decade-old talk on Wayland link to this video Wayland has been the default on Fedora and Arch w/ GNOME since around 2018, 5 years ago. It became the default on Debian w/ GNOME in 2019, 4 years ago. So yes, long time coming. KDE took longer but it's now finally ready.