4 ms·
It's much too short to read an output, interpret it and realize you have to interrupt But often you type something, realize it's wrong while you are typing but
by jsjshsbd 2y ago
It's much too short to read an output, interpret it and realize you have to interrupt
But often you type something, realize it's wrong while you are typing but not fast enough to stop your hand from pressing [Enter]
That is one of the only situation 100ms would be enough to safe you
That being said, the reason in the article for 100ms is just confused commander. Why would anyone:
1) encode a Boolean value as 0/1 in a human readable configuration
2) encode a duration as a numeric value without unit in a human readable configuration
Both are just lazy
- Reason077 2y ago> "Why would anyone ... encode a Boolean value as 0/1 in a human readable configuration" It may be lazy, but it's very common!
- grayhatter 2y agolaziness is a virtue of a good programmer. why demand many char when few char do trick? also > Why would anyone [...] encode a duration as a numeric value without unit in a human readable configuration If I'm only implementing support for a single unit, why would you expect or want to provide a unit? What's the behavior when you provide a unit instead of a number? > but not doing that extra work is lazy no, because while I'm not implementing unit parsing for a feature I wouldn't use, instead I'm spending that time implementing a better, faster diff algorithm. Or implementing a new protocol with better security, or sleeping. It's not lazy to do something important instead of something irrelevant. And given we're talking about git, which is already very impressive software, provided for free by volunteers, I'm going to default to assuming they're not just lazy.
- SoftTalker 2y agoAbsolutely. When I'm booting up an unfamiliar system and trying to catch the BIOS prompt for something non-normal, even 5 seconds is often too short. For me to notice that the prompt has been given, read "PRESS DEL KEY TO ENTER SETUP, F11 FOR BOOT OPTIONS, F12 FOR PXE BOOT" (or whatever), understand it, look for the F11 key on the possibly unfamilar keyboard on my crash cart, and press it, can often take me more than 5 seconds. Especially if it's not a single key required but a control sequence. Maybe I'm slow. I always change these prompts to 10 seconds if they are configurable. Or I'll make a label with the options and stick it on the case so I can be prepared in advance.