Hacker News new | ask | show | jobs
by expathacker 2694 days ago
2038? Does this have to do with Epoch time ending somehow?
2 comments
philwelch 2694 days ago
Yeah, coal-powered computers can only handle 32-bit integers ;)
link
cozzyd 2694 days ago
In 2038, the coal company clocks roll back to 1901, when all was good in the world for them.
link
kbutler 2694 days ago
...to 1970...
link
jcranmer 2694 days ago
No, it rolls over to 1901. time_t is a signed value, and 2038 is when it rolls over from 2³¹ - 1 to -2³¹. That would be 2 billion seconds before 1970, or 1901.
link
est31 2694 days ago
... which was a very great year for lignite mining: https://www.oeko.de/fileadmin/oekodoc/BET2017-Hermann-Oeko-I...
link
cozzyd 2694 days ago
If our Unix forefathers had the foresight to make time_t unsigned, then we wouldn't have to worry about this problem until after 2100.
link
2038AD 2693 days ago
I would guess, when originally suggested, it was $current_year + 2 decades.
link