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

11–20 of 248 posts

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

#11

Post by diggan »

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…

Isn't Le Mans more of a "endurance" race though, especially compared to F1? It would be interesting to see the difference in reaction ability between racers from the two, I could see it being different.

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

#12

Post by politelemon »

I agree that 'prompt' should be the value to set if you want git autocorrect to work for you. I'd however want that the Y is the default rather than the N, so that a user can just press enter once they've confirmed it.

In any case it is not a good idea to have a CLI command happen without your approval, even if the intention was really obvious.

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

#13

Post by schacon »

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.

I'm curious if the startup time, plus the overhead of Git trying to figure out what you might have meant is significant enough to give you enough time to realize and hit ctrl+c. In testing it quickly, it looks like typing the wrong command and having it spit out the possible matches without running it takes 0.01-0.03s, so I would venture to guess that it's still not enough time between hitting enter and then immediately hitting ctrl-c, but maybe you're very very fast?

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

#14

Post by schacon »

diggan wrote: post #11
schacon wrote: post #7

Earlier quoted context omitted.

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…

Isn't Le Mans more of a "endurance" race though, especially compared to F1? It would be interesting to see the difference in reaction ability between racers from the two, I could see it being different.

I feel like in the "racing / git crossover" world, that's pretty close. :)

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

#15

Post by pacaro »

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…

I've also worked with engineers who have raced LMP. It's largely pay-to-play and this is one of those professions where if you're the right person, in the right place, at the right time, you might be able to afford it.

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

#16

Post by misnome »

politelemon wrote: post #12

I agree that 'prompt' should be the value to set if you want git autocorrect to work for you. I'd however want that the Y is the default rather than the N, so that a user can just press enter once they've confirmed it. In any case it is not a good idea to have a CLI command happen without your approval, even if the intention was really obvious.

Yes, absolutely this. If I don’t want it to run, I will hit ctrl-c.

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

#17

Post by mscdex »

This seems a bit strange to me considering the default behavior is to only show a suggested command if possible and do nothing else. That means they explicitly opted into the autocorrect feature and didn't bother to read the manual first and just guessed at how it's supposed to be used.

Even the original documentation for the feature back when it was introduced in 2008 (v1.6.1-rc1) is pretty clear what the supported values are and how they are interpreted.

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

#18

Post by dusted »

I think it makes sense, if I typed something wrong, I often feel it before I can read it, but if I already pushed enter, being able to ctrl+c within 100 ms is enough to save me. I'm pretty sure I've also aborted git pushes before they touched anything before I put this on, but this makes it more reliable.

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

#19

Post by atonse »

331c8c71 wrote: post #5
1970-01-01 wrote: post #2

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

Seconds or milliseconds (e.g. if the setting must be integer) would've been fine as they are widely used. Deciseconds, centiseconds - wtf?

Falls squarely within the "They were too busy figuring out whether they could do it, to ask whether they SHOULD do it"

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

#20

Post by dusted »

1970-01-01 wrote: post #2

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

at least fractions of a second, 250 would already be much more noticble.. 100 is a nice compromise between "can't react" and "have to wait", assuming you're already realizing you probably messed up
Post reply on HN