Why is Git Autocorrect too fast for Formula One drivers?

Unit choice and “deciseconds”

• Many find deciseconds (0.1 s) an obscure and confusing unit; milliseconds or seconds would be more conventional in software.
• Others argue deciseconds are a reasonable granularity for human-facing UI delays: humans feel 200–300 ms vs 1+ s, but not 20 vs 30 ms.
• Several comments stress that the real problem is not stating the unit anywhere; people reasonably assumed 1 was a boolean, not “1 decisecond.”
• Some note deciseconds are more common in certain industrial control systems (e.g., in Japan), possibly influencing the choice.

Human reaction time vs 100 ms

• Many argue 100 ms is below typical human reaction times; even elite athletes and esports players are around 150–200 ms.
• Skeptics say it’s unrealistic to see an autocorrect suggestion and decide to cancel in that window.
• Others counter that typing corrections are often “anticipatory” rather than pure stimulus–response: you notice a typo as you’re hitting Enter and already have Ctrl‑C “queued.”
• There’s disagreement whether that actually lets you reliably beat 100 ms; some did ad‑hoc tests and reported ~250–320 ms reaction times.

Autocorrect feature design and safety

• Several see automatic execution of guessed commands as inherently dangerous, especially for “unsafe” operations (push, destructive commands).
• Some users like autocorrect with a longer delay or prompt, saying they often catch typos mid-command and abort.
• Others call the entire feature creeping featurism: unnecessary complexity that encourages sloppier typing.

Configuration semantics and units

• Strong sentiment that time settings should always encode units in the name or value (e.g., timeout_ms, 5s), and ideally use a “duration type,” not a bare integer.
• The reuse of a formerly-boolean setting as a numeric timeout is widely criticized; it creates ambiguity where 1 could mean “true” or “0.1 s.”
• This is tied to a broader complaint about untyped config formats and magic conversions (e.g., 1 as bool, integers as times, YAML-style boolean coercions).

Broader views on Git UX

• Multiple comments use this as another example of Git’s unfriendly, ad‑hoc CLI and options that accreted via small patches.
• Some praise Git’s underlying data model but see the interface as a pile of confusing edge cases like this one.