Storing UTC is not a silver bullet

Re:Storing UTC is not a silver bullet by z3t4 on Wednesday March 27, 2019 @02:47PM (#19504500)

I like unix time. But its not perfect either. Soon we will have a new y2k problem where unix time can no longer fit into an integer. Anyone remember the y2k problem ? People predicted major catastrophes as the year was encoded with two digits. But no one is talking about unix time.

[ Parent | on HN ]

Re:Storing UTC is not a silver bullet by feedbeef on Wednesday March 27, 2019 @10:16PM (#19508542)

I wonder what kind of fallout will come from the year 2038 problem [1]. It appears the Deep Impact space probe was lost to a 32-bit clock rollover bug, which portends some level of disaster come 2038.

1. https://en.wikipedia.org/wiki/Year_2038_problem

[ Parent | on HN ]

Re:Storing UTC is not a silver bullet by tombert on Wednesday March 27, 2019 @07:29PM (#19507351)

This will certainly be a problem for older apps, but anything I've done in the last 10 years I've been dev'ing, literally every library I've used for Unix time uses a 64 bit integer, which should last for a few million years.

[ Parent | on HN ]

Re:Storing UTC is not a silver bullet by z3t4 on Sunday April 07, 2019 @06:46PM (#19600439)

Some programming languages still don't have 64 bit integers!

[ Parent | on HN ]