Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why is Git Autocorrect too fast for Formula One drivers?

blog.gitbutler.com

Post reply on HN
Print view View original

61–70 of 248 posts

Re: Why is Git Autocorrect too fast for Formula One drivers?

#61

Post by xeonmc »

schacon wrote: post #7
mike-the-mikado wrote: post #4

I'd be interested to know if any F1 drivers actually use git.

Not sure, but I do personally know two high profile Ruby developers who regularly race in the LMP2 (Le Mans Prototype 2) class - DHH and my fellow GitHub cofounder PJ Hyett, who is now a professional driver, owning and racing for AO ( https://aoracing.com/ ). I mostly say this because I find it somewhat fun that they have raced _each other_ at Le Mans last year, but also because I've personally seen both of them type…

Maybe we can pitch to Max Verstappen to use Git to store his sim racing setup configs.

Re: Why is Git Autocorrect too fast for Formula One drivers?

#63

Post by otherme123 »

kittikitti wrote: post #8

I sometimes have this realization as I'm pressing enter and reflexively press ctrl+c. As someone whose typing speeds range from 100 to 160 WPM, this makes sense. Pressing keys is much different from Formula One pit stops.

Not about pit stops. They talk about pro drivers with highly trained reflexes, looking at a red light knowing that it will turn green in the next 3 seconds, so they must push a pedal to the metal as fast as they can. If they react in less than 120ms is considered a jump start.

As for 100WPM, which is a very respectable typing speed, it translates to 500 CPM, less than 10 characters per second, and thus slightly above 100ms per keypress. But Ctrl+C are two key presses: reacting to type them both in under 100 ms is equivalent to a writting speed above 200WPM.

Even the fastest pro-gamers struggle to go faster than 500 actions (keypresses) per minute (and they use tweaks on repeat rates to get there), still more than 100ms for two key presses.

Re: Why is Git Autocorrect too fast for Formula One drivers?

#64

Post by orangepanda »

dullcrisp wrote: post #57
orangepanda wrote: post #49

Earlier quoted context omitted.

The slapping device would need to build inertia for you to feel the slap. Is 10ms enough for that?

I think if it's spring-loaded then definitely. (But it's 100ms, not 10ms.)

Assuming the best case scenario of feeling the slap in 90ms, it would leave 10ms to abort the command. Or did the 90-180ms range refer to something else?

Re: Why is Git Autocorrect too fast for Formula One drivers?

#65

Post by [deleted] »

brazzy wrote: post #44
shawabawa3 wrote: post #35

Earlier quoted context omitted.

In this case the reaction starts before you hit enter, as you're typing the command So, you type `git pshu ` and realise you made a typo before you've finished typing. You can't react fast enough to stop hitting enter but you can absolutely ctrl+c before 100 more ms are up

> you can absolutely ctrl+c before 100 more ms are up Not gonna believe that without empirical evidence.

[deleted]

Re: Why is Git Autocorrect too fast for Formula One drivers?

#66

Post by WalterBright »

> Originally, if you typed an unknown command, it would just say "this is not a git command".

Back in the 70s, Hal Finney was writing a BASIC interpreter to fit in 2K of ROM on the Mattel Intellivision system. This meant every byte was precious. To report a syntax error, he shortened the message for all errors to:

    EH?
I still laugh about that. He was quite proud of it.

Re: Why is Git Autocorrect too fast for Formula One drivers?

#67

Post by WalterBright »

WalterBright wrote: post #66

> Originally, if you typed an unknown command, it would just say "this is not a git command". Back in the 70s, Hal Finney was writing a BASIC interpreter to fit in 2K of ROM on the Mattel Intellivision system. This meant every byte was precious. To report a syntax error, he shortened the message for all errors to: EH? I still laugh about that. He was quite proud of it.

I've been sorely tempted to do that with my compiler many times.

Re: Why is Git Autocorrect too fast for Formula One drivers?

#68

Post by bot403 »

TonyTrapp wrote: post #9
UndefinedRef wrote: post #3

Earlier quoted context omitted.

Maybe he meant dekaseconds? Still weird though..

It reads like the intention was that turning the parameter (0/1) command into an integer parameter, where the previous value enabled = 1 should behave reasonably close to the old behaviour. 1 deciseconds is arguably close enough to instant. If the parameter were measured in seconds, the command would always have to wait a whole second before executing, with no room for smaller delays.

No, smaller delays Do some think that 900ms, or 800, or some other sub-second value is really what we need for this error condition? Instead of, you know, not creating errors?

Re: Why is Git Autocorrect too fast for Formula One drivers?

#69

Post by Etheryte »

shawabawa3 wrote: post #35
Etheryte wrote: post #24

Earlier quoted context omitted.

Maybe worth noting here that 100ms is well under the human reaction time. For context, professional sprinters have been measured to have a reaction time in the ballpark of 160ms, for pretty much everyone else it's higher. And this is only for the reaction, you still need to move your hand, press the keys, etc.

In this case the reaction starts before you hit enter, as you're typing the command So, you type `git pshu ` and realise you made a typo before you've finished typing. You can't react fast enough to stop hitting enter but you can absolutely ctrl+c before 100 more ms are up

I'm still pretty skeptical of this claim. If you type 60 wpm, which is faster than an average human, but regular for people who type as professionals, you spend on average 200ms on a keystroke. 60 standard words per minute means 300 chars per minute [0], so 5 chars per second which is 200ms per char. Many people type faster than this, yes, but it's all still very much pushing it just to even meet the 100ms limit, and that's without any reaction or anything on top.

[0] https://en.wikipedia.org/wiki/Words_per_minute

Re: Why is Git Autocorrect too fast for Formula One drivers?

#70

Post by GuB-42 »

1970-01-01 wrote: post #2

Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.

Deciseconds (100ms) are not a bad unit when dealing with UI because it is about the fastest reaction time. We can't really feel the difference between 50 ms and 150 ms (both feel instant), but we can definitely feel the difference between 500 ms and 1500 ms. Centiseconds are too precise, seconds are not enough. Also, it is also possible that the computer is not precise enough for centiseconds or less, making extra precision a lie.

Deciseconds are just uncommon. But the problem here is that the user didn't expect the "1" to be a unit of time but instead a boolean value. He never wanted a timer in the first place.

By the way, not making the unit of time clear is a pet peeve of mine. The unit is never obvious, seconds and milliseconds are the most common, but you don't know which one unless you read the docs, and it can be something else.

My preferred way is to specify the unit during the definition (ex: "timeout=1s") with a specific type for durations, second is to have it in the name (ex: "timeoutMs=1000"), documentation comes third (that's the case of git). If not documented in any way, you usually have to resort to trial and error or look deep into the code, as these values tend to be passed around quite a bit before reaching a function that finally makes the unit of time explicit.

Post reply on HN