The post is a GitHub gist with a tiny Swift app and launch setup that records a single screen pixel every 10 seconds on the MacBook Neo. The odd effect is that it makes the cursor lag disappear. The author’s writeup suggests the lag shows up when macOS stops using a hardware cursor and falls back to drawing the cursor through the framebuffer or compositor, and that periodic screen capture somehow prevents the system from entering that bad state.
Most of the useful discussion landed on one point: the workaround is gross, but the underlying bug is serious because cursor latency is one of the fastest ways to make a machine feel broken. People with graphics experience thought the likely failure is not the screenshot itself doing anything magical, but that it changes which rendering path macOS uses. Several comments pointed to the switch from hardware cursor to
software cursor as the smoking gun. Others argued the real trigger could be power management or a fullscreen low-power rendering path, because changing cursor size can also help and older macOS bugs around detached fullscreen compositing behaved similarly.
The strongest technical pushback was against oversimplified explanations of “software cursor.” On a modern composited desktop, the cursor is usually another layer or
plane, not code scribbling pixels into the framebuffer by hand. That matters because the bug is probably in how
WindowServer, the display controller, and
GPU fences coordinate cursor updates when macOS changes modes, not in some ancient save-and-restore pixel routine. A few people noted that only reverse engineering or Apple source access would settle the exact cause.
There was also a practical side thread: some users are not seeing the issue at all on Neo hardware or on older macOS builds, which makes this look like a regression or a mode-specific bug rather than a universal flaw in the machine. A smaller side conversation appreciated the gist as a nice example of a minimal macOS app bundle and embedded Swift scripting, but that was secondary to the main reaction that Apple should fix the cursor path instead of leaving users to keep the compositor artificially awake forever.