> Like all problems, it isn't a technical it is political.
Could you explain how/why? Is it about specializing in specific hardware/firmware?
Could you explain how/why? Is it about specializing in specific hardware/firmware?
In open source often no one really cares about a suggested feature or even a submitted pull requests. It means additional work for the project maintainers - discussing design, reviewing code and handling of eventual bug fixes. Often the person who made a PR disappears leaving all future bugs the problem of the maintainer. So naturally project maintainers are risk averse and often say no to new features. Things end up not being implemented, not because it's technically difficult, or there's nobody willing to do the work, but because the incentives don't align.
The above opinion applies to open source in general as I've witnessed during the past decade. I'm not describing any projects that are related touchpad or input that I've been interacting with lately.
----
Because of sub-system ownership and crossing boundaries between window managers and input handlers. Just getting folks to recognize the problem and agree on how and where it should get fixed is the major hurdle. When software is overly modularized it both prevents many classes of optimizations and it forces certain communication patterns. Conway's Law [1] in reverse, teams will be split across component boundaries and solving Desktop Linux issues will require a level of coordination I am not sure the community is up to.
Writing the if the statements isn't the issue, coordinating and agreeing on the problem is.