Timeline for Why do many programming languages and applications use integer instead of floating point to represent time?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 17, 2022 at 7:21 | comment | added | gnasher729 | Thousand years from now we need 35 bits for seconds and have 18 bits for sub seconds, which gives 4 microseconds. Not worrying. And there is extended precision (80 bit) which changes it to 2 nanoseconds. | |
| Aug 6, 2019 at 18:39 | history | edited | Theraot | CC BY-SA 4.0 | added 20 characters in body |
| Aug 6, 2019 at 18:15 | history | edited | Theraot | CC BY-SA 4.0 | added 110 characters in body |
| Aug 6, 2019 at 18:04 | comment | added | Theraot | @RobertHarvey "Of course a quartz watch isn't the most accurate way to keep time. The most accurate way we have now is with an atomic clock. But did you know this an atomic clock still uses the vibration of a quartz crystal to keep time it's just that it also uses atoms of cesium to tweak the vibrations of the quartz crystal if it seems to be drifting off? So, yeah even an atomic clock uses a quartz crystal." – Steve Mould | |
| Aug 6, 2019 at 17:59 | comment | added | Robert Harvey | Well, yeah. Or Cesium atoms. | |
| Aug 6, 2019 at 17:32 | history | answered | Theraot | CC BY-SA 4.0 |