Unix time coverage in:

32-bit signed integer:
from 1902 to 2038

32-bit unsigned integer:
from 1970 to 2102

64-bit signed integer:
from 280 billion years before big bang
to 306 billion years after big bang

64-bit unsigned integer:
from 1970
to 600 billion years after big bang

The last one seem impractical.

For context 1970 (or "now") is approximately 13.8 billion years after big bang.

If we want our unixtime in milliseconds that still 585 million years of coverage.

I still vote signed for that one.

Show thread

@zatnosk When we approach roll over of the signed 64bit int, we can just start using the rolled over numbers for a ~while~ before we get actual ambiguity

@LovesTha "for a while" being approximately 20 times the current age of the universe.

@zatnosk I just found out about the Year 2038 Problem a little while ago and it blew my mind... I also admit I didn't know about "leap seconds" and the difference between UTC and GMT 😊

Highly recommended podcast unfortunately German only

Chaosradio: Das Jahr-2038-Problem

I learned about the #y2k38 problem in the early 2000s after reading a couple of posts by John Titor.
#JohnTitor claimed to be a time traveler from 2036 who travelled back in time to look for a certain computer to deal with the integer overflow issue.

@FiXato @gabor that story actually indirectly showed up when I tried to figure out when exactly signed 32bit would overflow.

@zatnosk @FiXato I see so you kind of re-invented the 2038 problem 😂

@gabor @FiXato no, I just couldn't remember the date because it's arbitrary.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!