Email or username:

Password:

Forgot your password?
12 comments
Ludovic Archivist Lagouardette

@ErikUden A recently released game blames the end of the world on people being lazy fucks and not fixing the Y2038 bug

OrntLaOkro

@ErikUden Eine Bildbeschreibung, die den Witz für Unwissende erklärt. Das ist ja richtig gut!

Boss aka Alfred E. Neumän

@ErikUden ach bis dahin gibts doch kein 32bit mehr!! (wegduck)

Simon Zerafa :donor: :verified:

@ErikUden

Don't forget about the 2K36 issue!

The 64-bit timestamp used by NTPv3 and earlier will cycle from February 7, 2036 at 06:28:16 back to January 1, 1900 🫤🤷‍♂️

Tanquist

@ErikUden
I never saw that one coming! It did remind me of #recycling #paper #calendars. You don't need to buy a #2024 #calendar if you have one laying around from 1940, 1968 or 1996.

patter

@ErikUden I worked with someone who did that for storing order times in an e-commerce database. If you wanted a month's sales out, you'd have to calculate the timestamps, instead of "SQL, select April"

Scott Crawford

@ErikUden Looks like I may get to trot out my mad COBOL skillz again 😂

Josef 'Jeff' Sipek

@ErikUden The 2038 page has a month name that ends with “ber” when the overflow happens in January 2038. Yeah, I know… I’m nuts… #timenuts

Josef 'Jeff' Sipek

@ErikUden and the overflow would be to December 1901, not January 1970. (I’m a hopeless case…)

Go Up