Live data from Hacker News

Linux touchpad: preliminary project funding, survey results

bill.harding.blog

101–110 of 174 posts

Re: Linux touchpad: preliminary project funding, survey results

#101
post #97

Earlier quoted context omitted.

And the Apple touchpad doesn't hinge at all! The "click" reaction you get when you press it is simulated by a set of force sensors and an actuator that vibrates the trackpad to simulate a click.

Apple trackpads used to hinge 10 years ago.

Actually, they used to sell a trackpad that did that until last year!

Re: Linux touchpad: preliminary project funding, survey results

#102
post #47

Earlier quoted context omitted.

So many companies made unsubscribing too hard that I wouldn’t even try it with github.

I just did this, and it's very easy. After you cancel, GH even puts up a multiple-choice "why did you cancel?" survey, and one of the options is "wanted to make a one-time donation".

Perhaps they should make that an official option at that point…

Re: Linux touchpad: preliminary project funding, survey results

#103
post #16
post #2

> There's currently a gaping chasm between the 35 sponsors who have supported the project on GitHub so far (thank you!!!) and the 309 poll respondents who indicated they would donate to this cause.

Well, let me put it this way. I would donate $250 to fix it. I think that's how much working support for touch, trackpad, and pen input would be worth it to me. I would donate $0 for a stranger on the internet to try to fix it themselves. I would donate $0 and advise others not to donate with an approach where there isn't even a developer driving this themselves ("Give us money, and we'll hire someone to fix it" appr…

> I have some ideas on how we might calibrate the acceleration curve to better match macOS, but it would be handy if anyone else has bright ideas on how they would attempt to quantify the touchpad acceleration curve on macOS

Reverse engineer the drivers and platform frameworks?

Re: Linux touchpad: preliminary project funding, survey results

#104
I've been using Ubuntu since 2009, two HP laptops and zero problems with the touchpad. I used the first one with Windows for two years and the touchpad behaved better with Ubuntu than with Windows. I think the improvement was two finger scrolling instead of sliding on the right edge. I used only Ubuntu on the second laptop so I can't do any comparison but I never felt anything wrong with the touchpad. HP nc8430 and ZBook 15 first gen.

Re: Linux touchpad: preliminary project funding, survey results

#105
post #82

I'm faintly curious, how does the MacOS "Touchpad Experience" referenced in question #1 differ from the Windows one? (Or any other OS?) (Background to my ignorance: While I do (very) occasionaly use MacOS, I usually default to the terminal as it's more familiar... and probably spend most (60-70%) of my time connected to linux or unix-like systems via cli/ssh... from a Windows system.) Are we talking touch gestures or…

much much much better: - super smooth. Scrolling and everything just feels right. They do a lot of low level software magic to make that happen. Off topic: If you ever try to reimplement a scroll view on iOS you will see how much effort is needed to make it smooth - even if you have access to all the same APIs - biiiig trackpad. I find this especially important when I have a big external monitor plugged in. I can eas…

I've done some reverse engineering of the macOS Spaces implementation and it is really all the way through the stack; Dock creates animation transactions and everything in WindowServer to make it work. You really need deep integration to have something like that be smooth and work well.

Re: Linux touchpad: preliminary project funding, survey results

#106
post #74

Earlier quoted context omitted.

Yep, Apple really nailed it with that choice. Not only can you use GUI key combos in the terminal, but also you can use terminal line editing key combos in the GUI. That's something that seems like it ought to be possible in Linux, but afaik it is not.

One thing one my wish list of things that will probably never happen is an extensible EMACs, Jupyter hybrid with a full on highly extensible dependently typed programming language. By keeping the specification of the components as abstract as possible, one could reinterpret the same code to give a completely different and customizable user experience. Probably with a lens based GUI toolkit for interactive widgets. I…

OK, I'll bite that sandwich.

Can you expand some of these points? I fail to understand (I need an ELI5, first principles)

I think I get the premise, EMACs/Jupyter hybrid with ext. prog. lang. (+1 for typed).

> By keeping the specification of the components as abstract as possible, one could reinterpret the same code to give a completely different and customizable user experience.

Custom UX is my pet peeve, has been forever since the 1990s. I have intuitions but no clear understanding of what you mean here. Does that essentially mean decoupling model/view, a more modular or stateless metaphor?

> Probably with a lens based GUI toolkit for interactive widgets.

lens? (impossibly hard for me to Google what that generic word refers to, I just tried)

————

I'd like to 'get' to the essence of the paradigm you're suggesting. What the 'magic' is, its endgame, what it 'feels' or looks like.

Re: Linux touchpad: preliminary project funding, survey results

#108

I can hardly tell the difference between my razer stealth linux touchpad and my workprovided macbook. Even based on the feedback, it seems that most people are okay with their touchpad experience and are more interested in advanced features like multitouch. Having this said, for myself this is a tough sell. I'm concerned that I would donate and I won't be able to tell the difference between this and some placebo driv…

I'm in exactly the same spot with a (reasonably old 2017 model) Dell XPS. Wayland with libinput has been a JOY to use compared to basically anything I've used in linux before. I tried running an X based DE about 2 years ago on this machine and actually went back to running it in a VM in windows because the touchpad felt so shoddy. No problems at all with the current setup. Can barely tell the different between my wor…

Yeah I don't have a problem with either my Asus Zenbook or my HP Envy.

Reading through the comments it sounds like the real problem is Thinkpad trackpads suck for whatever reason and this is somehow getting extrapolated to "Linux trackpads suck".

Re: Linux touchpad: preliminary project funding, survey results

#109

This is still the most frustrating thing about Linux for me. I have two Thinkpads, a T460 running Windows from my employer, and a T560 running Ubuntu as my personal. Their touchpad hardware is, of course, identical. The experiences couldn't be more different. When I first got the machine, I spent weeks fighting with the driver, trying to figure out how a single number can represent four lines on two dimensions to def…

This is one of the reasons I like WSL, it uses the windows drivers for things but I get the Linux user land (and much of the kernel with WSL2).

Re: Linux touchpad: preliminary project funding, survey results

#110
post #106

Earlier quoted context omitted.

One thing one my wish list of things that will probably never happen is an extensible EMACs, Jupyter hybrid with a full on highly extensible dependently typed programming language. By keeping the specification of the components as abstract as possible, one could reinterpret the same code to give a completely different and customizable user experience. Probably with a lens based GUI toolkit for interactive widgets. I…

OK, I'll bite that sandwich. Can you expand some of these points? I fail to understand (I need an ELI5, first principles) I think I get the premise, EMACs/Jupyter hybrid with ext. prog. lang. (+1 for typed). > By keeping the specification of the components as abstract as possible, one could reinterpret the same code to give a completely different and customizable user experience. Custom UX is my pet peeve, has been f…

Maybe they're referring to this? https://en.wikibooks.org/wiki/Haskell/Lenses_and_functional_...

As for the "abstract specification", I interpret it as decoupling the view from the model too, but maybe expressing how you can represent the model? Like "option" being representable by a dropdown or radius buttons. I don't know, I agree it's vague.

Post reply on HN