4 ms·
And the millisecond it is not. ...unless you're talking about computer programming instead of physics, in which case one uses counts of milliseconds, microseco
by nitrogen 16y ago
And the millisecond it is not.
...unless you're talking about computer programming instead of physics, in which case one uses counts of milliseconds, microseconds, or nanoseconds. Also remember that integers are valid floating point numbers, so after(100) is ambiguous in the context of computer programming (as pointed out by the prior poster).
- kragen 16y agoIf you have floating-point numbers, there's no reason to use milliseconds, microseconds, or nanoseconds instead of seconds, except to deliberately obfuscate your code, or if you need more than 53 bits of precision.
- nitrogen 16y agoSure, if you're running JavaScript on a CPU with a beefy FPU there's no reason now, but you're still going against decades of ingrained behavior and potentially affecting performance on embedded systems.