Why is Git Autocorrect too fast for Formula One drivers?

Post by Aerroon » Mon, Jan 20, 2025, 7:53 PM UTC

legacynl wrote: post #218

arp242 wrote: post #199

Earlier quoted context omitted.

Basically, some people can consistently respond faster. The 100ms figure just isn't accurate. I don't have extensive resources/references at hand, but I've read about this a few times over the years.

> I don't have references ... but I've read about this a few times over the years. Yeah well, I did a psych bsc and I'm telling you that it's impossible. It's certainly possible for people to do and notice things way faster than that, like a musician noticing a drummer being a few ms off beat, or speedrunners hitting frame perfect inputs, but in those cases the expectation and internal timekeeping is doing most of th…

Post by crazygringo » Mon, Jan 20, 2025, 9:23 PM UTC

yencabulator wrote: post #232

crazygringo wrote: post #228

Earlier quoted context omitted.

Not really. I don't want to have a type for an integer in seconds, a type for an integer in minutes, a type for an integer in days, and so forth. Just like I don't want to have a type for a float that means width, and another type for a float that means height. Putting the unit (as oppose to the data type ) in the variable name is helpful, and is not the same as types. For really complicated stuff like dates, sure ma…

> I don't want to have a type for an integer in seconds, a type for an integer in minutes, a type for an integer in days, and so forth. This is not how a typical Duration type works. https://pkg.go.dev/time#Duration https://doc.rust-lang.org/nightly/core/time/struct.Duration.... https://docs.rs/jiff/latest/jiff/struct.SignedDuration.html

Post by WalterBright » Mon, Jan 20, 2025, 10:03 PM UTC

zubairq wrote: post #151

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.

Pretty cool.. I had no idea Hal was such a hacker on the personal computers in those days... makes me think of Bitcoin whenever I hear Hal mentioned

Post by twic » Mon, Jan 20, 2025, 11:25 PM UTC

TeMPOraL wrote: post #214

twic wrote: post #201

Earlier quoted context omitted.

I do something similar in Java by taking a java.time.Duration in any method dealing with time. We don't have the snazzy literal syntax, but that means users have to write: someMethodDealingWithTime(Duration.ofMillis(10)); someMethodDealingWithTime(Duration.ofSeconds(1)); someMethodDealingWithTime(50); // does not compile Since these often come from config, i also have a method parseDuration which accepts a variety of…

> i also have a method parseDuration which accepts a variety of simple but unambiguous string formats for these, like "10ms", "1s", "2h30m", "1m100us", "0", "inf", etc. I did that too with parsers for configuration files; my rule of thumb is that the unit has to always be visible somewhere anywhere a numeric parameter occurs - in the type, in the name, or in the value. Like e.g.: // in config file: { ..., "timeout":…

Post by zxvkhkxvdvbdxz » Tue, Jan 21, 2025, 12:57 AM UTC

adzm wrote: post #140

zxvkhkxvdvbdxz wrote: post #118

Earlier quoted context omitted.

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.

> But you can possibly sense the difference between 2 and 3 deciseconds (200 ms and 300 ms) after some practice. At 120bpm a sixteenth note is 125ms, the difference is very obvious I would think