shatteredgate

13 ms·

91.
by shatteredgate 5y ago
>If somebody else does the work for him he'll still reject it. I would like to see this statement where he said he would reject it, I searched and couldn't find any statements to that effect. If it was rejected for some technic
92.
by shatteredgate 5y ago
>synaptics gets the job done and libinput doesn't, it's really that simple as far as I'm concerned. From a maintenance perspective it is unfortunately not that simple. I sympathize with your frustration and personally I to
93.
by shatteredgate 5y ago
>Creating a "standardized experience" like Windows usually means that configurability goes right out the window. It's how you get abominations like dconf or the GNOME music player I don't understand how you connected
94.
by shatteredgate 5y ago
It's not really true at all. The libinput developer blogged about why having more configuration options has historically not actually been good for the project, or for users of the synaptics driver: https://who-t.blogspot.co
95.
by shatteredgate 5y ago
>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
96.
by shatteredgate 5y ago
There isn't any political pressure from Red Hat. They're often the only company that does any work on the input stack in userspace, without them it would probably not even exist or be stuck in a very old state. You can complain bu