Memes

45665 readers

969 users here now

Rules:

Be civil and nice.
Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago

MODERATORS

[email protected]

1415

just wait, it could get worse.... (feddit.de)

submitted 1 year ago by [email protected] to c/[email protected]

205 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 173 points 1 year ago (25 children)

Remember when Y2K was going to potentially end the world, but it didn't thanks to experts working 'round the clock?

Remember when corporations turned around and got pissy because Y2K was successfully avoided, claiming that it was all a big hoax?

Remember how it's now taught in some places that Y2K was a hoax and you can't trust experts?

No wonder the world struggled with COVID.

[–] [email protected] 29 points 1 year ago* (last edited 1 year ago) (3 children)

Are you ready to go through it again soon?

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

The year 2038 problem (also known as Y2038, Y2K38, Y2K38 superbug or the Epochalypse) is a time formatting bug in computer systems that represent times after the time 03:14:07 UTC on 19 January 2038.

The problem exists in systems which measure Unix time – the number of seconds elapsed since the Unix epoch (00:00:00 UTC on 1 January 1970) – and store it in a signed 32-bit integer. The data type is only capable of representing integers between −(231) and 231 − 1, meaning the latest time that can be properly encoded is 231 − 1 seconds after epoch (03:14:07 UTC on 19 January 2038). Attempting to increment to the following second (03:14:08) will cause the integer to overflow, setting its value to −(231) which systems will interpret as 231 seconds before epoch (20:45:52 UTC on 13 December 1901). The problem is similar in nature to the year 2000 problem.

A lot of old PC hardware simply couldn't scale to modern needs. On the plus side, things like virtualization and 64-bit architecture are helping solve issues like this.

[–] [email protected] 13 points 1 year ago

We actually recently lived through some of the work arounds for Y2K causing issues again. Look up the Y2020 issue. A lot of the fixes for Y2K only pushed the problem out 20 years.

load more comments (2 replies)

load more comments (23 replies)