The real story behind Wayland and X

Channel:Linux.conf.au 2013 -- Canberra, Australia · Length:45:35 · Published:2014-11-23 · Views:46423

Watch on YouTube

Summary

X.Org developer Daniel Stone explains the history and technical limits of the X Window System and why Wayland was created, debunking myths from forum comments. He covers topics such as network transparency and blocking calls.

Why HN recommends it

HN uses it as the go-to answer to claims that Wayland is unnecessary, from a developer who knew X's codebase well.

It is quite fun and eye opening, he clearly knows his subject better than most of the comments. — HN, 2020

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

This criticism looks like "free as beer and I know better". 1. The old, mostly working thing waits your commit 2. That new thing can have some help too I recommend developers story about this "mostly working thing" (2014) [1]. It is quite fun and eye opening, he clearly knows his subject better than most of the comments. Wayland demo worked almost from day one. I've run it in 2010 [2]. But we nee… — sergeykish, 2020-10
Really recommend that speech as well since it's give good understanding what's wrong with X11 and why Wayland was created. The real story behind Wayland and X: [VIDEO] — SXX, 2020-08
> I've seen commentary from people who have worked intimately on both protocols and implementations of both who consider Wayland to have the better architecture. For those interested in details: [VIDEO] — vetinari, 2023-02
Well, you can imagine some evil behind everything if you wish.. Or just look at a technical video about it: [VIDEO] I don’t see these conteos regarding linux, especially goddamn desktop with the minuscule user share. It is literally a hobby thing for some graphics enthusiasts without any sort of money. Yeah sure, red hat or whatever.. — kaba0, 2021-04
It would be nice to reproduce phoronix results. Do they run in GNOME shell? What if I run in Sway? What exactly they expect of Selenium? I've heard gedit startup example. Sorry, I can't continue until you've watched presentation [1] > gedit startup: > 130 blocking InternAtom calls > 34 blocking GetProperty calls > 116 property change requests > blocking because Xlib is terrible > usually spends 2… — sergeykish, 2020-10

Related videos