Wayland and Weston: 8 years of production devices
summary
Wayland and Weston have eight years in production and first hit millions of users via a set-top box around the 0.85 era; they now run in set-top boxes, smart TVs, watches and even as a Wayland server in ChromeOS (Exosphere) to host Android apps. Weston serves both as a production compositor and a lab for new features (kernel mode‑setting, libliftoff), and recent releases add Weston profiling and introspection tools used to close the gap from prototype to reliable, low-latency production deployments.
AI-written summary · about
chapters (24)
- 0:00Introduction to Wayland and Weston
- 1:06Wayland’s evolution since 2008
- 3:22Pre-history and early development
- 6:01Stone Age and first public contributions
- 8:09Bronze Age and first releases
- 10:17Five years of growth and adoption
- 13:00Advanced stage and new features
- 15:10Maturity and stabilization phase
- 17:24Development trends over time
- 21:47Wayland’s success as a window system
- 22:52Community transition challenges
- 25:46Key takeaways and lessons learned
- 26:10Tightly scoped and minimal design
- 30:13Optimizing for open drivers and best practices
- 32:23Importance of protocol versioning
- 33:05Handling leadership transitions
- 34:31Building Linux infrastructure
- 37:44Documentation struggles and solutions
- 40:32Toolkits vs mid layers
- 41:15Barriers to entry and contributor growth
- 46:41Testing and validation improvements
- 48:31Project stages and audience shifts
- 49:54Community health and periodic reassessment
- 50:19Q&A
related talks
30mHello Wayland, Goodbye X11 - The year of the Linux desktop!
24mThe AGL Wayland Compositor, Present and Future Design Work
32mThe Modern Linux Graphics Stack on Embedded Systems
23mWayland Goal Status Update
10mLightning Talk: The AGL Wayland Compositor
49mBuilding End-user Applications on Embedded Devices with WPE
05mBuilding Graphical Appliances Made Easy
49mEmbedding WPE WebKit - from Bring-up to Maintenance