> it’s an artifact of the fragmented ecosystem of Linux
You mentioned literally two frameworks gtk and qt, which both use libinput, i.e. one thing. How is this fragmented?
> it’s an artifact of the fragmented ecosystem of Linux
You mentioned literally two frameworks gtk and qt, which both use libinput, i.e. one thing. How is this fragmented?
I considered it as fragmented b.c. the reason it was implemented this way (instead of implementing in the toolkit) was mostly because one can’t coordinate big changes in at least three big libraries (vendor drivers + libinput + Qt/GTK) to achieve something relatively small (inertia scrolling) when Apple can just decide to ‘fix everything related’ if one decides to adopt a new feature.
Not that fragmentation is a necessarily bad thing, but it’s not great in these cases.
That was my question. So macOS has one blessed toolkit working nicely and everything else feeling "wrong". So this has nothing at all to do with being "fragmented" but simply says "apple has one good toolkit and lots of bad ones".