"Fix" MacBook Neo Cursor Lag: Record 1 Pixel of the Screen Every 10 Seconds

Original Article ↗ Hacker News Discussion ↗

A cursor lag bug on Apple’s low-cost MacBook Neo has prompted users to share a hacky workaround: periodically recording a single pixel to force macOS to treat the pointer as a software-drawn cursor instead of using hardware overlay. Commenters debate how egregious it is for a modern OS—especially Apple, long associated with smooth UI—to ship with such a flaw, trade war stories about similar GPU and power-saving quirks, and explore the technical reasons hardware/software cursor transitions can introduce latency. Many see the fix as an amusing but revealing indictment of today’s complex graphics stacks and shifting Apple design priorities.

Overall reaction to the Neo cursor bug

  • Many see cursor lag as a “cardinal sin” in UX: the pointer is described as the user’s “embodiment” in the computer, so stutter makes the whole system feel broken.
  • Commenters compare this unfavorably to 1980s–90s systems where cursors were reliably smooth, even on far weaker hardware.
  • Several say this feels like something that should be treated as a critical, show‑stopper bug.

The proposed 1‑pixel recording fix

  • The script periodically records a pixel to force WindowServer to composite the cursor instead of using a hardware overlay.
  • Some praise it as a minimally invasive, practical workaround for a highly annoying issue.
  • Others call it a “terrible” cure that keeps the GPU awake or forces extra compositing, and worry users will forget it’s running long after Apple fixes the real bug.
  • A similar “hacky fix” pattern appears in anecdotes: scripts hashing periodically to stop coil whine, touching files to prevent USB drives from spinning down, etc.

Technical discussion: hardware vs software cursor

  • Several detailed posts explain hardware cursors (separate overlay planes, position registers) versus software cursors (drawn into a composited framebuffer).
  • One theory: lag happens during transition from hardware to software cursor, possibly due to waiting for GPU command queues or fences to flush.
  • Others argue modern compositors just re-render layers each frame; they dispute older “save/restore under the cursor” descriptions as outdated.
  • It’s unclear exactly what macOS is doing on the Neo; commenters say real answers would require driver or WindowServer code.

Alternative mitigations and related bugs

  • Changing the cursor size slightly has historically fixed some GPU/compositing bugs; on the Neo, a noticeably larger size is reported as necessary, and may not always help.
  • Detached fullscreen low‑power modes on macOS are mentioned as a source of past rendering glitches.

Comparisons and broader Apple commentary

  • Some Linux users report similar cursor lag under heavy load or on specific setups; others say they’ve never seen it, so prevalence is disputed.
  • Multiple comments lament a perceived decline in Apple’s UX rigor, arguing the Neo’s low price plus visible glitches undermines the “it just works” brand.

Side threads

  • Brief digression into Swift’s guard syntax and its advantages.
  • Notes on using Swift as a scripting language via shebang.
  • Anecdotal pranks and nostalgic discussion of old hardware and UI design principles.