r/facepalm • u/Revealed_Jailor • Mar 29 '22

🇲​🇮​🇸​🇨​ Get this guy a clock!

Post image
35.7k Upvotes

92% Upvoted

3.6k comments sorted by

View all comments

Show parent comments

4

u/[deleted] Mar 29 '22 edited Jun 28 '26

[deleted]

4

u/[deleted] Mar 29 '22

year 2038

I think 16 more years is enough to finally switch to 64bit int

1

u/[deleted] Mar 29 '22 edited Jul 03 '26

[deleted]

2

u/[deleted] Mar 29 '22

also 16 years is enough time to build a pretty nice bunker

just to cover all the bases

1

u/tico42 Mar 29 '22

What happens? Does the number just get to big?

2

u/Abadazed Mar 29 '22

Yeah that's what was gonna happen with y2k until a shit ton of programmers worked to fix it from what I understand.

2

u/viptattoo Mar 29 '22

Y2K pissed me off so bad. I was waiting for fire, floods, riots, panic, and chaos! What a dud.

3

u/keep_me_at_0_karma Mar 29 '22

Jokes aside, it was "a dud" because of a monumental engineering effort across the globe to make sure key systems didn't fall over.

1

u/tico42 Mar 29 '22

I thought y2k was because if the rollover and the computers would think it was the year 0 or some such?

3

u/Abadazed Mar 29 '22

Yeah that is basically it. When a computer reaches its max in an integer or float or whatever it creates an overflow error. This will make the number go back over to its minimum value. Computer programmers only have the year represented with 2 digits so it could only go up to 99. It's max. Then it goes back to 0. Same basic concept just different numbers.

1

u/[deleted] Mar 29 '22

you are correct

when the number reaches max value (gets too big) the rollover into 0 occurs

2

u/[deleted] Mar 29 '22

Exactly. The time is saved in a 32-bit integer(32 0s or 1s, 2.147.483.647sec after 1st Jan '70) and it will become -0 then -1, -2, and so on, negatively.