"Write a single library to handle all input devices, it'll be easy" they said...

Channel:linux.conf.au · Length:46:54 · Published:2020-01-17 · Views:21499

Watch on YouTube

Summary

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.

Why HN recommends it

Cited for insight into the hard realities of Linux input handling and libinput's thinly staffed maintenance.

One of the folks behind both Wayland and X gave a fantastic talk on the issues and the hell. — HN, 2024

Software architecture & design · Linux & open-source ecosystems

Subtitles (excerpt)

good afternoon everyone please welcome Peter to the stage who is going to talk about writing a single library for all your devices thank you my name is peter hundra I work for Red Hat up in Brisbane and I've been working with improved devices for proximately 10 to 12 years now so surprisingly I'll be talking about input devices today specifically about how we handle them why we handled him that way and what has changed over the last few years because a quite a number of things have changed so let's go back to this to the start of a few years ago so we have a nice beautiful storyline in the beginning there was chaos so a few years ago everyone was using X and X has more history than high school curriculum these days so for most things when you're giving a talk like this always pays off to look at what X is doing scratch your head for a while sway a bit and then try to figure out why this doing that at this point I would like to know for if there's any PhD guys in the audience so I apologize this talk is about Linux only some of the bits especially historical pits might may apply to the bsts but yeah well sorry so x-height handles input devices works that it has a number of different input drivers

On 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. [VIDEO] — indrora, 2024-08
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. [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] — 5e92cb50239222b, 2021-12
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] [VIDEO] — Akronymus, 2021-11
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. [VIDEO] — scaladev, 2020-12

Related videos