Linux Touchpad Like MacBook Update: 2023 Progress on Smooth Scrolling

Original Article ↗ Hacker News Discussion ↗

Apple’s trackpads are widely praised as the gold standard, and many laptop users say poor touchpad behavior on Linux and Windows is a major barrier to switching away from Macs. Commenters examine why replicating Apple’s smooth, inertial scrolling and gesture handling is so hard in the PC and Linux world, pointing to fragmented responsibility across drivers, compositors, and apps, weaker hardware–software integration, and limited incentives for vendors to invest. While some report that modern Wayland desktops with good hardware now feel close to macOS, others still find inconsistent scrolling, missing “kinetic” behavior, and hard‑to‑tune settings across toolkits like GTK, Qt, and Firefox.

Overall sentiment on touchpads

  • Many commenters say MacBook trackpads are far ahead of typical PC / Linux / Windows laptops; switching away “feels like going back in time.”
  • Others report modern GNOME/KDE on good hardware (especially MacBooks or ThinkPads) now feels “on par” or even better than macOS.
  • Some users say they’ve never had issues with Linux touchpads and don’t understand what the project is trying to fix.

Why Apple’s trackpads feel better

  • Long-term vertical integration: Apple controls hardware, firmware, OS, drivers, and UI, and targets few device models.
  • Trackpads are essentially iPhone/iPad-class multitouch sensors with refined acceleration, palm rejection, and inertia.
  • Scrolling feels “physical”: pixel-precise, low-latency, with realistic momentum and rubber‑banding.

Technical challenges on Linux

  • Responsibility for scrolling/gestures is fragmented across libinput, display server, compositor, window manager, toolkits (GTK/Qt), and individual apps.
  • Kinetic/inertial scrolling is often implemented at the app/toolkit layer, leading to inconsistent behavior between apps (e.g., GTK vs Qt vs browsers).
  • Earlier synaptics drivers had working “fake” kinetic scrolling but were dropped; libinput rejects synthetic events and advanced per-device tuning.
  • Ongoing debate: where should inertia and configuration live (driver vs compositor vs toolkit), and how to handle focus changes without weird side effects.

Hardware, market, and ROI factors

  • PC OEMs are integrators using commodity touchpad ICs (Synaptics, Alps) and rushed firmware; quality and tuning vary widely.
  • Many buyers optimize on visible specs (RAM, CPU) rather than input quality, so vendors under-invest.
  • In FLOSS, cross-layer fixes are hard to coordinate and not clearly “owned,” and perceived ROI for deep polish is low.

Current non-Apple landscape

  • Windows “Precision Touchpad” and some Chromebooks offer very good experiences; ChromeOS uses proprietary drivers and custom scrolling paths.
  • Wayland GNOME/KDE on recent hardware generally has decent gestures and kinetic scrolling, but configuration (especially scroll speed) and consistency remain pain points.
  • Project progress is seen as incremental and slow; some users feel no visible benefit yet.

Input device preferences

  • Strong camps exist: external mice, trackpads (often Mac-style), trackpoints, and trackballs; ergonomics and RSI experiences differ widely.