"Write a single library to handle all input devices, it'll be easy" they said...
linux.conf.au1 HN recommender · recommended in 1 month, 2020-2024
21K views · 6 years ago · talk · evergreen
Peter Hutterer's linux.conf.au 2020 talk on creating libinput, the unified userspace input library, and the difficulties of handling the many quirks of input devices.
Cited for insight into the hard realities of Linux input handling and libinput's thinly staffed maintenance.
34:14"What UNIX Cost Us" - Benno Rice (LCA 2020)
linux.conf.au
218K views • 6 years ago
1:02:52Joanna Rutkowska: Towards (reasonably) trustworthy x86 laptops
media.ccc.de
27K views • 10 years ago
31:38Cory Benfield - Building Protocol Libraries The Right Way - PyCon 2016
PyCon 2016
15K views • 10 years ago
34:00User-level threads....... with threads. - Paul Turner - Google
Linux Plumbers Conference
41K views • 13 years ago
![[Linux.conf.au 2013] - The real story behind Wayland and X](https://i.ytimg.com/vi/cQoQE_HDG8g/hq2.jpg)
45:35[Linux.conf.au 2013] - The real story behind Wayland and X
HackersOnBoard
35K views • 13 years ago
42:20Writing a Wayland Compositor in Zig - Isaac Freund
Zig SHOWTIME
26K views • 6 years ago
12:31OSCON 2010: Rob Pike, "Public Static Void"
O'Reilly
119K views • 16 years ago
30:50Why Google Stores Billions of Lines of Code in a Single Repository
@Scale
317K views • 11 years ago
![The Forgotten Art of Structured Programming - Kevlin Henney [C++ on Sea 2019]](https://i.ytimg.com/vi/SFv8Wm2HdNM/hq2.jpg)
1:29:27The Forgotten Art of Structured Programming - Kevlin Henney [C++ on Sea 2019]
cpponsea
245K views • 7 years ago
45:35The Real Story Behind Wayland and X - Daniel Stone (linux.conf.au 2013)
Mladen Mijatov
104K views • 13 years ago
23:57GopherCon 2016: The Design of the Go Assembler - Rob Pike
Gopher Academy
116K views • 10 years ago
44:35Object-Oriented Programming is Bad
Brian Will
2.6M views • 10 years ago
1:03:31Brian Goetz - Stewardship: the Sobering Parts
ClojureTV
39K views • 11 years ago
7:16Unix and Google
FOAM
9K views • 10 years ago
43:30Are we stuck with the same Desktop UX forever? | Ubuntu Summit 25.10
Canonical Ubuntu
509K views • 11 months ago
41:06"Unison: a new distributed programming language" by Paul Chiusano
Strange Loop Conference
45K views • 7 years ago
32:02Autonomous Testing and the Future of Software Development - Will Wilson
The Linux Foundation
7K views • 7 years ago
51:27Google I/O 2012 - Go Concurrency Patterns
Google for Developers
894K views • 14 years ago
41:19Stuart Sierra - Components Just Enough Structure
ClojureTV
36K views • 12 years ago
35:32Cheng Lou - On the Spectrum of Abstraction at react-europe 2016
ReactEurope
63K views • 10 years ago
4 comments from Hacker News
There are some advantages and disadvantages of the approach. However, there's just stuff that X assumes that isn't true anymore. A good example is how it handles input. How many cursors does a screen have? One machine? okay, One input device? One of the folks behind both Wayland and X gave a fantastic talk on the issues and the hell. ▶ this video
That "dev" you're criticizing here has been developing libinput solo since the beginning. He asked for help numerous times and never received any. So either step up and do the work, or stop complaining. ▶ this video libinput is yet another of those fundamental libraries that receive almost no developer attention, but get all the blame when something goes wrong: link
Yeah it takes a LOT of work to hide it [1] Also: For some stuff I want to be able to use the "arcane" parameters for some really obscure task where it is just the right flag or something. [1] ▶ this video
The whole usermode side of input handling depends on a project (libinput) that's been developed by a single guy over the last decade. He asked for help numerous times, reminding everyone that libinput has a bus factor of one, and received none. So either go ahead and help, or stop complaining. ▶ this video