3 ms·
Its always amazing to realize how big 2^64 really is. 2^32 Flicks is about 6 seconds (which can be enough, but still not that useful), but 2^64 is over 800 year
by zokier 9y ago
Its always amazing to realize how big 2^64 really is. 2^32 Flicks is about 6 seconds (which can be enough, but still not that useful), but 2^64 is over 800 years, which should be quite enough for anything needing this sort of precision. It would be actually pretty nifty to have this in eg. `struct timespec` and overall base rtc around Flicks
- BeeOnRope 9y agoWhy would it be nifty to base the underlying format exposed by the OS time APIs and real-time clocks be based on a unit that happens to be a integer divisor of a bunch of common audio and video formats in 2018? Sure, flicks seems like a useful tool for people working in those fields, but what about the rest of us? Seems a bit short sighted, or at least extremely unusual for the average person who doesn't care how audio or video is encoded but still deals with high precision time. If I'm interested in CPU performance, should I suggest that time be denominated in units that are compatible with common CPU frequencies?
- psyc 9y agoIndeed. The majority of my longs only need a few bits more than an int. The largest value I’ve ever needed was a 58-bit index/key for a combinatorial thing.
- planteen 9y ago> It would be actually pretty nifty to have this in eg. `struct timespec` and overall base rtc around Flicks I disagree. We already have enough confusion with time and another unit at the level of timespec is not helpful IMHO. The SI unit of time is the second and 1/sec is Hz, which are used everywhere in science and engineering. I don't want another non-SI time unit getting thrown around and messed up in calculations. 800 years doesn't even come close to covering a single precession rotation of the Earth (26,000 years). The timespec structure already covers either 2^61 seconds (7.3 * 10^11 years) at an accuracy of a nanosecond. So that's enough to cover 72x the current age of the universe. I have some experience in astronomical calculations. Things are already quite confusing there, since you often need a monotonically increasing time scale (without seconds leap seconds). There is already enough confusion if someone is in TAI, GPS, or UTC time. Julian day, commonly used in ephemeris calculations, works back to 4713 BC. Believe it or not, we sometimes want to get positions going back that for things like computing proper motions from ancient star catalogs, correlating supernova explosions, and various other recorded historical astronomical events.
- wahern 9y ago> There is already enough confusion if someone is in TAI, > GPS, or UTC time Don't forget BCT: https://en.wikipedia.org/wiki/Barycentric_Coordinate_Time https://en.wikipedia.org/wiki/Barycentric_Coordinate_Time