2 ms·
> The end-user shouldn't even care about this They may want to care because not every device will be in the hw database at the outset. Or the existing descript
by zozbot234 7y ago
> The end-user shouldn't even care about this
They may want to care because not every device will be in the hw database at the outset. Or the existing description may be incomplete, and fail to account for something that libinput supports. Good hardware support starts from users "scratching their own itch" by experimenting with "advanced", less-strictly-supported options to reach the best combination for their hardware, and perhaps their niche use cases. Testability is a red herring because only a few advanced options will ever be applicable; the issue is that they're different options for different cases.
- cycloptic 7y agoIt's not a red herring. Those advanced options still need to be tested and maintained. If no one tests and maintains those options, they will break and users will complain again and you're right back where you started. The idea is that it's better to just remove them instead of creating a false expectation that they're going to work. I personally would agree with that decision, at least in this case anyway. In libinput, people who understand the problem and are willing to work with the developers and contribute upstream can edit the hardware quirks. The maintainer has also blogged about this: https://who-t.blogspot.com/2018/06/libinput-and-its-device-quirks-files.html https://who-t.blogspot.com/2018/06/libinput-and-its-device-q...