Fork me on GitHub
#off-topic
<
2021-09-26
>
sova-soars-the-sora03:09:37

Or maybe a new solar epoch that can handle 8-9 planet settings :d

Ben Sless04:09:11

Future proof it and make it galactic coordinates, then time stamps include location and velocity relative to the galactic center

valtteri05:09:32

Galactic center sounds brittle to me wrt scalability. 😉 Once we go intergalactic we’re in the same time zone mess. You also need to consider alternative histories because information between entities travels at speed of light at max.

Ben Sless05:09:48

I was actually thinking that once you go intergalactic just forget a universal time measure and have each galaxy as its own time zone

valtteri06:09:34

And then you’re asked to make an intergalactic fintec system with full transaction and solid history support. You start thinking “oh crap why didn’t we model time as interaction of all entities and their causal interactions since the epoch (singularity)“. Then you start programming and you create the Universe. 🤯

Ben Sless06:09:13

When you aren't living in a simulation as a battery for machines, just to keep track of financial transactions

kulminaator11:09:21

Thinking of calendar libraries and the likely meltdown of random software in 2038 .. should look for a way to retire in 17 years 😄

sova-soars-the-sora12:09:49

Y2k38 ... just rolls off the tongue

andy.fingerhut17:09:04

How many time/date libraries still use seconds since 1970-Jan-01 stored in a 32-bit number?

p-himik17:09:14

It's not only libraries. Everything that's 32-bit is potentially affected, lots of embedded stuff.

phronmophobic17:09:35

I assume there’s still plenty of dbs out there where someone used 32bits to store the time

andy.fingerhut00:09:19

Yeah, of course there is a Wikipedia page on this issue, and it mentions file systems and databases as places where 32-bit times in seconds are sometimes used: https://en.wikipedia.org/wiki/Year_2038_problem