3 ms·
Maybe he meant dekaseconds? Still weird though..
by UndefinedRef 2y ago
Maybe he meant dekaseconds? Still weird though..
- TonyTrapp 2y agoIt 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.
- bot403 2y agoNo, smaller delays <1s are also a misdesign here. Have we all forgotten we're reacting to typos? It's an error condition. It's ok that the user feels it and is inconvenienced. They did something wrong. 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?
- schacon 2y agoWe had this debate internally at GitButler. Deci versus deca (and now deka, which appears to also be a legit spelling). My assumption was that 1 full second may have felt too long, but who really knows.
- a3w 2y agodeci is 1/10, deca is 10/1. So decisecond is correct.
- schacon 2y agoI understand, I meant I tried to say the word “decisecond” out loud and we debated if that was a real word or if I was attempting to say “deca” which was understandable.
- zxvkhkxvdvbdxz 2y agoIt's very standardized (SI), meaning 1/10:th. Althought not so commonly used with seconds. You might be more familiar with decimeters, deciliters, decibels or the base-10 (decimal) numbering system.
- quesera 2y agoAlso "decimate" which used to mean "kill 1/10th of the soldiers", but now apparently means "destroy (almost) entirely". :)
- CRConrad 2y agoSure, deca- as in "decade" is understandable. But why would deci- as in "decimal" be any less understandable?