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

Channel:HackersOnBoard · Length:45:35 · Published:2013-03-27 · Views:34939

Watch on YouTube

Summary

A linux.conf.au 2013 talk by a Wayland developer who previously worked on X, telling the history of X and why Wayland was created. It covers X's hardware abstraction and architecture and why they became problematic for modern graphics.

Why HN recommends it

Whenever Wayland versus X comes up, HN points to this talk as the authoritative explanation from an X maintainer of why X was replaced.

a great presentation by one of the guys behind wayland, who worked on X a lot before — HN, 2021

Operating systems & kernels · Linux & open-source ecosystems · Computer graphics & rendering

Subtitles (excerpt)

Okay, the first talk for today is by Daniel Stone and it's the real story behind Wayland and X. Uh Daniel currently works at Collabora where he's been working full-time on Wayland for the past year or so, having recently overhauled the input subsystem. He's also written a couple of graphics drivers in his time and has recently moved from Melbourne to Finland and more recently to the UK. So, it's nice to welcome him back here. So, thank you very much for coming to talk to us today, Daniel. Turn this on. Brilliant. Thank you. Also, hi. Um yeah, as you can probably guess, I'm here to talk about Wayland and X. Um pretty much what they actually are um since my experience has been that no one has any idea. Um Everything you read on the internet about it will be wrong. Um it's ridiculous all that. However, there are the occasional gems, which I'd recommend strongly. But this, I think, is pretty much the state of play, uh which I'd like to change. So, ideally, I'd like everyone in this room at the end of it, even if you don't agree with me, that's fine, but just stop posting stuff that's blatantly wrong in LWN comments. Cuz I'm really bored of it. Sorry, LWN, if you're here. There's actually a cool Collabora slide coming up.

On Hacker News

Please have a look at an X maintainers very own presentation: [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) — kaba0, 2022-02
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. [VIDEO] — tux1968, 2021-03
Here you are: [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 … — kaba0, 2021-03
Here's a decade-old talk on Wayland [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. — dralley, 2023-11
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 graphics[1]. [1]: [VIDEO] — cyphar, 2019-11

Related videos