Cursorless is alien magic from the future
Voice‑driven coding tools like Talon and the Cursorless extension for VS Code are being hailed as a viable — and in some cases faster — alternative to keyboard-based editing, especially for developers with RSI, arthritis or other hand injuries. Commenters explore how Cursorless overlays and AST‑aware commands compare to traditional workflows in Emacs/Vim and to AI coding assistants, and note trade‑offs such as latency, learning curve, and suitability for shared offices. A large portion of the conversation branches into personal RSI experiences, covering ergonomics, strength training, posture, trigger‑point therapy, and psychosomatic pain models as people trade strategies for staying able to program long term.
RSI Experiences and Treatments
- Many commenters report serious wrist/hand/arm pain from programming, gaming, instruments, or mouse use; others with similar habits report no RSI at all and see this as genetics or physiology.
- A wide range of fixes are cited: trigger-point massage, dry needling, ice-water immersion, wrist supports, changing typing technique, stretching, posture work, and changing sleep positions.
- Several note specific “aha” moments: identifying nerve compression from sleeping with bent elbows, discovering tension from “ready to click” mouse posture, or adjusting how arms move instead of fingers.
- Some had surgeries (carpal tunnel, nerve issues) with mixed long‑term outcomes.
Exercise, Ergonomics, and Hardware
- Many say strength training, climbing, deadlifts, pulling exercises, and mid‑day walks significantly reduced or eliminated pain; others warn heavy lifting can aggravate existing injuries.
- There is disagreement over “see a doctor/PT first”: some say essential for existing RSI, others call this overcautious and emphasize starting light and sensible.
- Hardware changes that helped: split/tented and low‑force keyboards, vertical mice, trackballs, trackpoints, thumb clusters, remapped modifiers, standing desks, correct desk height, simpler chairs, and moving the mouse location.
- Some report that just fixing desk/monitor/chair height or not resting wrists eliminated symptoms.
Voice Coding, Talon, and Cursorless
- Strong enthusiasm for Cursorless + Talon as a viable or even faster way to code, especially as “insurance” against hand disability.
- Learning curve is acknowledged as steep; several liken it to vim or Emacs mastery and recommend learning before you’re in pain.
- Questions about editor support: currently best with VS Code; Emacs/JetBrains integration is partial, with tree‑sitter‑based AST operations seen as a core advantage.
- Concerns include using voice in shared/open offices and accent recognition issues; some suggest directed or throat mics as potential mitigations.
AI-Assisted Coding vs Cursorless
- Some argue GPT‑4 inside IDEs already handles many structural edits via natural language, reducing the need to learn a special voice UI.
- Others counter that latency, privacy, and reliability make local, deterministic tools like Cursorless preferable, and that latency still limits AI workflows.
Accessibility and UX Issues
- Colorblind users find the colored “hats” confusing; others note Cursorless can switch to shapes.
- Eye‑tracking is discussed as an alternative pointing mechanism, but latency and practicality for frequent operations are questioned.
Psychological and Psychosomatic Perspectives
- Multiple anecdotes describe apparently psychosomatic RSI or back pain resolving after adopting mind–body frameworks (e.g., viewing pain as neuroplastic/expectation‑driven).
- Others caution that not all pain is mental, emphasize imaging and medical evaluation, and stress that these approaches should complement, not replace, medical care.