>rewrite everything from scratch without taking into account that some things you’re throwing out actually work really well This is not what happened. The syna

>rewrite everything from scratch without taking into account that some things you’re throwing out actually work really well This is not what happened. The synaptics driver and libinput were/are maintained by the same person, who has written about it extensively and explained why the approach in the synaptics driver does not work well. Specifically, some of the problems with the synaptics driver have directly led to decisions in libinput. You may want to read some of their blog posts if you haven't: https://who-t.blogspot.com/2016/12/xf86-input-synaptics-is-not-synaptics.html https://who-t.blogspot.com/2016/12/xf86-input-synaptics-is-n... 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-... https://who-t.blogspot.com/2016/03/why-libinput-does-not-have.html https://who-t.blogspot.com/2016/03/why-libinput-does-not-hav... It may seem like a good idea on its surface to have tons of abstractions and features and extension mechanisms, but that fades away when you get deal with the bug reports over a period of years and get to see all the problems it causes.