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

171–180 of 248 posts

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

#171

Post by cma »

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.

Earliest I've seen with 'Eh?' as an interpreter response is RAND's JOSS:

https://en.wikipedia.org/wiki/JOSS#/media/File:JOSS_Session....

https://en.wikipedia.org/wiki/JOSS

They had about 5KB of memory but comparing to the Intellivision the machine weighed about 5,000lbs.

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

#172

Post by dotancohen »

furyofantares wrote: post #102
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 run a wordle spinoff, xordle, which involves two wordle puzzles on one board. This means you can guess a word and get all 5 letters green, but it isn't either of the target words. When you do this it just says "Huh?" on the right. People love that bit.

> People love that bit.

Add another seven Easter eggs, and people could love that byte.

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

#173

Post by arp242 »

amai wrote: post #166
newman314 wrote: post #152

For reference, Valtteri Bottas supposedly recorded a 40ms!!! reaction time at the 2019 Japanese Grand Prix. https://www.formula1.com/en/video/valtteri-bottas-flying-fin...

Most probably that was a false start: "World Athletics rules that if an athlete moves within 100 milliseconds (0.1 seconds) of the pistol being fired to start the race, then that constitutes a false start." https://www.nytimes.com/athletic/5678148/2024/08/03/olympics...

That value has also been criticised as too high.

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

#174

Post by fsckboy »

teraflop wrote: post #116
ekidd wrote: post #98

Earlier quoted context omitted.

Ed also uses "?" for "Are you sure?" If you're sure, you can type the last command a second time to confirm. The story goes that ed was designed for running over a slow remote connection where output was printed on paper, and the keyboard required very firm presses to generate a signal. Whether this is true or folklore, it would explain a lot. GNU Ed actually has optional error messages for humans, because why not.

https://www.gnu.org/fun/jokes/ed-msg.en.html "Note the consistent user interface and error reportage. Ed is generous enough to flag errors, yet prudent enough not to overwhelm the novice with verbosity."

>not to overwhelm the novice with verbosity

that doesn't make complete sense, in unixland it's old-timers who understand the beauty of silence and brevity, while novices scan the screen/page around the new prompt for evidence that something happened

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

#175

Post by dotancohen »

newman314 wrote: post #152

For reference, Valtteri Bottas supposedly recorded a 40ms!!! reaction time at the 2019 Japanese Grand Prix. https://www.formula1.com/en/video/valtteri-bottas-flying-fin...

I once had a .517 reaction time in a drag race. You know how I did that? By fouling too late. It was completely unrepeatable.

I'm willing to bet Bottas fouled that, too late (or late enough).

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

#176

Post by olddustytrail »

jakubmazanec wrote: post #161

> introduced a small patch > introduced a patch > the Git maintainer, suggested > relatively simple and largely backwards compatible fix > version two of my patch is currently in flight to additionally And this is how interfaces become unusable, through thousand small "patches" created without any planning and oversight.

Ah, if only the Git project had someone of your talents in charge (rather than the current band of wastrel miscreants).

Then it might enjoy some modicum of success, instead of languishing in its well-deserved obscurity!

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

#177

Post by LocalH »

mkesper wrote: post #142
egypturnash wrote: post #125

Earlier quoted context omitted.

C64 basic was tokenized into one byte, with the most significant bit set: https://www.c64-wiki.com/wiki/BASIC_token Each command could be typed in two ways: the full name, or the first two letters, with the second capitalized. Plus a few exceptions like "?" turning into the PRINT token ($99, nowhere near the PETSCII value for ?) and π becoming $FF. The tokens were expanded into full text strings when you would LIST t…

As far as I remember you couldn't even run these programs after listing anymore.

You could run them just fine as long as you didn't try to edit the listed lines if they were longer than two screen lines. The same is true for a C128 in C128 mode, except the limit is extended to 160 characters (four 40-column lines).

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

#178

Post by LocalH »

zxvkhkxvdvbdxz wrote: post #118
jonas21 wrote: post #93

Earlier quoted context omitted.

Milliseconds are a commonly-used unit. It doesn't really matter if 1 ms is too fine a granularity -- you'll just have to write "autocorrect = 500" in your config file instead of "autocorrect = 5", but who cares?

Sure, yes. But for human consumption, decisecond is something one can relate to. I mean, you probably cannot sense the difference in duration between 20 and 30 ms without special equipment. But you can possibly sense the difference between 2 and 3 deciseconds (200 ms and 300 ms) after some practice. I think the issue in this case was rather the retrofitting a boolean setting into a numerical setting.

And then you have the rhythm gamers who can adjust their inputs by 5 or 10ms. Hell, I'm not even that good of a player, but in Fortnite Festival, which has a perfect indicator whenever you're within 50ms of the target note timestamp (and a debug display that shows you a running average input offset) and I can easily adjust my play to be slightly earlier or slightly later and watch my average fall or climb.

Several top players have multiple "perfect full combos" under their belt, where they hit every note in the song within 50ms of the target. I even have one myself on one of the easier songs in the game.

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

#179

Post by junon »

jzwinck wrote: post #54
junon wrote: post #42

Earlier quoted context omitted.

If prompt is the default, mistyped scripts will hang rather than exit 1 if they have stdin open. I think that causes more problems than it solves.

That's what isatty() is for. If stdin is not a TTY, prompting should not be the default. Many programs change their defaults or their entire behavior based on isatty().

isatty() is spoofed in e.g. Make via PTYs. It's a light check at best and lies to you at worst.

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

#180

Post by Vinnl »

fsckboy wrote: post #174
teraflop wrote: post #116

Earlier quoted context omitted.

https://www.gnu.org/fun/jokes/ed-msg.en.html "Note the consistent user interface and error reportage. Ed is generous enough to flag errors, yet prudent enough not to overwhelm the novice with verbosity."

> not to overwhelm the novice with verbosity that doesn't make complete sense, in unixland it's old-timers who understand the beauty of silence and brevity, while novices scan the screen/page around the new prompt for evidence that something happened

If I didn't know any better, I'd have thought they weren't entirely serious.
Post reply on HN