5 ms·
Why does ChromeOS have all of the stuff that this project claims to be developing? Are they using proprietary touchpad drivers?
by jeffbee 6y ago
Why does ChromeOS have all of the stuff that this project claims to be developing? Are they using proprietary touchpad drivers?
- deleted 6y ago[deleted]
- laksdjfkasljdf 6y agoI still have no idea what this project is trying to do exactly. I always got decent multitouch on linux (when the touchpad is even recognized, but that's another problem).
- cxcorp 6y agoThe first post's discussion is here: https://news.ycombinator.com/item?id=17547817 https://news.ycombinator.com/item?id=17547817
- listennexttime 6y agoIt's okay, neither does the blog author. Despite their only value-add being a PM-role, they aren't doing a good job of that either. As evidenced by the fact that they've basically just resorted to doing tons of retrofit to bring benefits that already exist in Wayland to a legacy, deprecated, aging stack. (literally every single change listed). Also, it's no longer just about improving the touchpad (since libinput is already pushing the envelope there), and instead ... X11 Gestures? Okay? (Good luck to those brave enough to install a patched X11 from a PPA!) I feel sorry for the people who thought there was enough substance to donate. How this project progresses with increasingly less clarity and continues to be celebrated here deeply confuses me.
- p12tic 6y agoPovilas from the linked blog post here. The reasons why we chose the current path were explained in detail in the blog posts. Touchpad gestures was the most popular feature to implement. In order to do that we needed a good reason why all the other project maintainers would want to spend time discussing a feature with us. Wayland is the future, yes, but currently a lot of users are still on X which makes our argument much less convincing. Now we can say that touchpad gestures will soon be available everywhere and get their attention this way. I agree that X is legacy platform. Unfortunately it may still be used for quite some time. Core functionality such as screenshots and input record/replay is not universally available on Wayland. So X will still be used for significant amount of time. Please tell me what else I could explain to increase the transparency of the project and I'll try my best to do so. Thanks!
- tssva 6y agoDid you actually talk to other project maintainers and get feedback that they would only be interested if it were also available for X before starting down this path?
- p12tic 6y agoI haven't asked this question unfortunately. Adding touchpad gestures needs changes in every GUI toolkit library except GTK and every application we would like to support. So I trusted my own experience of seeing the amount of effort needed to contribute an improvement for niche use cases. To make matters worse, an initial OK from a maintainer often does not really mean a lot. What matters is the actual time commitment to discuss design and review patches. Issues that increase the amount of effort needed for long-term maintenance and end-user support tend to decrease maintainer engagement a lot. Wayland-only touchpad gestures splits the user-base long term and thus fits this criteria very well. At this moment I'm not really sure if I would go the same path had I knew all the information I know now. Having said that, we've only spent around a single man-month of effort working on this. In the grand scheme of things this detour is tiny.
- pmontra 6y ago> Core functionality such as screenshots and input record/replay is not universally available on Wayland. So X will still be used for significant amount of time. This is exactly my case. For me it's the difference between earning money or not working: I do some screen sharing with my customers every day. Wayland is not an option for me yet.
- octoberfranklin 6y ago> I still have no idea what this project is trying to do exactly. Raise funds, basically. Getting too specific about their development plans would interfere with that. People spend money based on emotion and shiny things. Yes, even Linux users.
- tpush 6y agoWhat driver stack is Google using for ChromeOS? Is it proprietary? I assume all the Chromebooks have decent touchpad functionality, can't that be mainlined or whatever?
- quaa55 6y agoi believe chromeos uses a custom kernel with their own stack.
- cmrdporcupine 6y agoThe whole ChromeOS UI and input stack is entirely different from a typical Linux desktop. I'm not sure there's a lot there that could be shared out to the Linux X11 desktop world.
- criddell 6y agoIs there something about the standard Linux input stack that makes it especially difficult to create a great touchpad experience? Apple got it right a long time ago, ChromeOS is good, and Windows is too. What's different about Linux?
- dastx 6y agoApple got it right because they built a stable api around it, and integrated all their applications with it. Linux hasn't got it right because there is still no unified api, even if there was, all apps must implement it to be useful. This is where OP push comes in. To make all of this possible through donations. You should read his older blog posts. They're worth a read.
- vetinari 6y agoApple supports only their own touchpads, ChromeOS also selected ones. Windows provides the great experience only for the Precision touchpads (i.e. not even to Apples under Bootcamp). Linux is expected to work with random crap, that even its vendors have given up upon. That's the difference.
- mdoms 6y agoLinux input still sucks with hardware that works great on other OS's.
- vetinari 6y agoThat's exactly not the point. The point was, that the other OSes picked specific hardware and they provide great experience only on that hand-picked hardware and nothing else. I specifically noted, that Apple touchpads do not work under Bootcamp as nicely as the Precision ones do, as an example.
- zelly 6y agoYes, Synaptics produces closed-source drivers for Windows and ChromeOS. ChromeOS also uses its own low-level input/graphics stack, not X11, so even if you had the code to it you wouldn't be able to just compile it on GNU/Linux.
- SahAssar 6y agoChromeOS has taken the path of Android on a lot of things, so drivers are usually hard to mainline.