9 ms·
Because it became a burden to maintain. https://who-t.blogspot.com/2016/04/why-libinput-doesnt-have-lot-of-config.html https://who-t.blogspot.com/2016/04/why-li
by archseer 6y ago
Because it became a burden to maintain. https://who-t.blogspot.com/2016/04/why-libinput-doesnt-have-lot-of-config.html https://who-t.blogspot.com/2016/04/why-libinput-doesnt-have-...
> In the old synaptics driver, we added options whenever something new came up and we tried to make those options generic. This was a big mistake. The driver now has over 70 configuration options resulting in a test matrix with a googolplex of combinations. In other words, it's completely untestable. To make a device work users often have to find the right combination of options from somewhere, write out a root-owned config file and then hope this works. Why do we still think this is acceptable? Even worse: some options are very specific to hardware but still spread in user forum examples like an STD during spring break.
- archseer 6y agoAlso note that the libinput maintainer was also the last synaptics maintainer. https://github.com/freedesktop/xorg-xf86-input-synaptics/commits/master https://github.com/freedesktop/xorg-xf86-input-synaptics/com...