3 ms·
Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.
by 1970-01-01 2y ago
Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.
- UndefinedRef 2y agoMaybe 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?
- 331c8c71 2y agoSeconds or milliseconds (e.g. if the setting must be integer) would've been fine as they are widely used. Deciseconds, centiseconds - wtf?
- atonse 2y agoFalls squarely within the "They were too busy figuring out whether they could do it, to ask whether they SHOULD do it"
- dusted 2y agoat 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
- gruez 2y agobetter yet, encode the units into the variable/config name so people don't have to guess. You wouldn't believe how often I have to guess whether "10" means 10 seconds (sleep(3) in linux) or milliseconds (Sleep in win32).
- synecdoche 2y agoThis may be something specific to Japan, which is where the maintainer is from. In the Japanese industrial control systems that I’ve encountered time is typically measured in this unit (100 ms).
- GuB-42 2y agoDeciseconds (100ms) are not a bad unit when dealing with UI because it is about the fastest reaction time. We can't really feel the difference between 50 ms and 150 ms (both feel instant), but we can definitely feel the difference between 500 ms and 1500 ms. Centiseconds are too precise, seconds are not enough. Also, it is also possible that the computer is not precise enough for centiseconds or less, making extra precision a lie. Deciseconds are just uncommon. But the problem here is that the user didn't expect the "1" to be a unit of time but instead a boolean value. He never wanted a timer in the first place. By the way, not making the unit of time clear is a pet peeve of mine. The unit is never obvious, seconds and milliseconds are the most common, but you don't know which one unless you read the docs, and it can be something else. My preferred way is to specify the unit during the definition (ex: "timeout=1s") with a specific type for durations, second is to have it in the name (ex: "timeoutMs=1000"), documentation comes third (that's the case of git). If not documented in any way, you usually have to resort to trial and error or look deep into the code, as these values tend to be passed around quite a bit before reaching a function that finally makes the unit of time explicit.
- userbinator 2y agoMy default for times is milliseconds, since that's a common granularity of system timing functions.