[Linux.conf.au 2013] - The real story behind Wayland and X
HackersOnBoard2 HN recommenders · recommended in 2 months, 2016-2023
35K views · 13 years ago · talk · evergreen
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.
Whenever Wayland versus X comes up, HN points to this talk as the authoritative explanation from an X maintainer of why X was replaced.
45:35The real story behind Wayland and X
Linux.conf.au 2013 -- Canberra, Australia
46K views • 11 years ago
45:35The Real Story Behind Wayland and X - Daniel Stone (linux.conf.au 2013)
Mladen Mijatov
104K views • 13 years ago
2:26Qt 5 based 3D Wayland compositor
Samuel Rødal
133K views • 14 years ago
7:42:30XDC 2020 - Day 1 - September 16, 2020
X.Org Foundation
24K views • 6 years ago
42:20Writing a Wayland Compositor in Zig - Isaac Freund
Zig SHOWTIME
26K views • 6 years ago
47:18The Tragedy of systemd
linux.conf.au
1.3M views • 7 years ago
45:33"A Political History of X" - Keith Packard (LCA 2020)
linux.conf.au
52K views • 6 years ago
46:06Gtk to Qt - a strange journey [linux.conf.au 2014]
Konstantin Bläsi
46K views • 12 years ago
49:16XFS: Recent and Future Adventures in Filesystem Scalability - Dave Chinner
Linux.conf.au 2012 -- Ballarat, Australia
29K views • 14 years ago
1:11:44DebConf 14: QA with Linus Torvalds
Adnan Hodzic
737K views • 12 years ago
53:44Console Hacking 2016 (33c3)
media.ccc.de
166K views • 9 years ago
53:55A Narrative History of BSD, Dr. Kirk McKusick
bsdconferences
30K views • 17 years ago
1:22:13HandmadeCon 2016 - History of Software Texture Mapping in Games
Molly Rocket
15K views • 9 years ago
46:54"Write a single library to handle all input devices, it'll be easy" they said...
linux.conf.au
21K views • 6 years ago
1:25:13The Origins of Linux—Linus Torvalds
Computer History Museum
659K views • 18 years ago
48:13RIP Windows: Linux GPU Gaming Benchmarks on Bazzite
Gamers Nexus
1.1M views • 11 months ago
1:04:04LISA11 - Fork Yeah! The Rise and Development of illumos
USENIX
310K views • 14 years ago
34:14"What UNIX Cost Us" - Benno Rice (LCA 2020)
linux.conf.au
218K views • 6 years ago
53:11EFI and Linux: the future is here, and it's awful - Matthew Garrett
Linux.conf.au 2012 -- Ballarat, Australia
77K views • 14 years ago
2:13Brigade 3.0 preview - Real-time path tracing
icelaglace
439K views • 12 years ago
6 comments from Hacker News
Here's a decade-old talk on Wayland ▶ 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.
Please have a look at an X maintainers very own presentation: ▶ 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)
Here you are: ▶ 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.
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. ▶ this video
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]: ▶ this video
> 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. ▶ this video