Sort of. There’s one coming up in 2038 where the number overflows a signed 32 bit integer. Anything using 32 bits for timestamps is going to get a wee bit confused.
This should be the last time that happens though as a 64 bit signed int can carry us to something like the year 290 billion
Easy, it’s 1715894564 after Jan 1 1970 00:00:00.
no its 1715898281 ffs
Out of curiosity, is there a “time limit” for this epoch value, or can it go on indefinitely?
Sort of. There’s one coming up in 2038 where the number overflows a signed 32 bit integer. Anything using 32 bits for timestamps is going to get a wee bit confused.
This should be the last time that happens though as a 64 bit signed int can carry us to something like the year 290 billion
!remindme 290000000000 years
I will be messaging you in 290000000000 years on 290000002024-05-17 06:08:00 UTC to remind you of this link.
CLICK THIS LINK to send a PM to also be reminded and to reduce spam.
Parent commenter can delete this message to hide from others.
Info Custom Your Reminders Feedback
You count up 1 second for each second from midnight on Jan 1st, 1970. The Unix epoch.
It can go on as long as we go on counting. Interestingly, it does ignore leap seconds.
No friend 7pm the night before. American East Coast in the 1960s.
Guys, I fucked up, its actually 1716002297. Apologies for the inconvenience