4 ms·
just report it in epoch seconds
by dylan604 3y ago
just report it in epoch seconds
- conductr 3y agothat's based on UTC, so just use UTC?
- dylan604 3y agobased on is not the same thing though is it? UTC is human readable even if it is not calculated correctly. yes, i'm saying that if you can read epoch seconds, you're not human. 1970-01-01 00:00:00 is always a give away that something is a foot
- conductr 3y ago"anchored on" then? I might be wrong but we're both talking about showing time as distance from the same starting point are we not? One's just more human readable so that's why I say why not just use that? Seconds since can be miscalculated too, especially if current time isn't known/reliable
- account42 3y agoI wish it was based on TAI though.
- queuebert 3y agoJulian Date
- dramm 3y agoOr stardate ¯\_(ツ)_/¯
- drivers99 3y agoOr Swatch Internet time (.beat time). No time zones, it's always UTC+1, with the day divided into 1000 beats.
- inopinatus 3y agoI will pass you the address of a struct timespec, please fill it in.
- yen223 3y agoJust make sure not to confuse it with epoch milliseconds!
- dathinab 3y agobetter: time encoded as a float of trecenti-seconds since year -8435 of the Georgian Calendar why? 'caus it hurt to even just think about implementing that anywhere
- account42 3y agoIgnoring leap seconds?