2038 Will Be the End of Time (In the Unix 32-Bit Timecode)

preview_player
Показать описание

The Year 2038 will cause nearly every modern computer to stop working if we don't prepare for it. This isn't because of some massive virus or degrading hardware, it has everything to do with how we keep time.

Nearly every computer in the history of computers keeps time using a 32-bit integer counting forward from 00:00:00 UTC on the 1st of January 1970, referred to as the epoch. This instant of time was set as the standard for modern computing systems, but there's a major problem. Seven seconds after 3:14 am UTC on the 19h of January 2038, the 32-bit integer storing this time data will run out of positions.

The problem is similar to the Y2K issue where a 2-digit value could no longer be used to encode the years 2000 or later, but different in that this 32-bit bug is related to Unix-like systems and the Unix time format.

These similarities to the Y2K bug have widely lead to the 2038 problem being known as the Unix Millennium Bug.

All images courtesy of Creative Commons or protected under Fair Use. For questions or concerns about the use of any media, please contact the page directly.
Рекомендации по теме
Комментарии
Автор

It should be noted (as it is in the video) that any computer that's connected to the internet will be fine. This is an issue with non-connected devices.

ConcerningReality
Автор

It’s basically the computer equivalent of trying to count to 6 on one hand.

ZanzibarBreeze
Автор

January 19 is my birthday. This will be a nice birthday present

aaronwitzel
Автор

Dear lord, this is an exact repeat of Y2K...

neosenju
Автор

"If they're still using this software (64bit) in the year 292, 277, 026, 596, then they deserve it."

disketteuser
Автор

Here's my prediction: some jerk will declare the end of the world is coming for every second for the next 10, 000 years, and it still won't happen.

MikeJones-nyyt
Автор

This is like an overly complicated Y2k scenario

modman
Автор

You can store higher than 32bit values on a 32bit computer, you need to use more registers but you can do it
you can even have 4096 bits value on 16bit computers if you want to there isn't really a limit, well the limit is the total amount of bits you can store on your slow) which is enormous

alkeryn
Автор

honestly im just stoked im gonna experience an event akin to y2k in my lifetime

frogberriez
Автор

Fun fact: We are closer to 2038 than to 2000

haleysettembre
Автор

as you said only modern computers, this will not be a issue in the future, as most tech used today would be replaced, and we will most likely fix it before.

shammar
Автор

Oh you youngin’s....Don’t remember Y2K do ya?

ryanhampson
Автор

Update : Now most devices either use an unsigned 32-bit or a 64-bit unix timecode, so January 19th, 2038 isn't a problem, the real problem comes out much later at Sunday, Febuary 7th, 2106 at 6:28:15 UTC.

candyneige
Автор

"The year 2038 will cause nearly every modern computer to stop working if we don't prepare for it."


32 bit computers, how modern.

WildRandomVideos-woxe
Автор

Technologies in 2038: Aight Imma head out.

MrDuckyHardy
Автор

Imagine our grandchildren and beyond talking about a “Year 21XX Problem” in the future with 64-bit devices and everyone is using 128-bits

ILoveQazaqstan
Автор

Dude people are smart, we will fix this guys dont worry

stanii
Автор

Replacing the 32-bit integer with a 64-bit one at the kernel level (something Linux has been doing for a long time and since version 5.6 regardless of whether or not the CPU is 64-bit) extends the overflow date to 292 billion years from now — so that sounds like a fix to me. Of course, this also breaks a lot of software that expects `time_t` to be 32-bit, because compilers throw errors when the types aren’t matching — so when an OS is updated in this way, a lot of apps must also be heavily modified to even compile, let alone run.

Also, Windows uses a completely different method to store time compared to the Unix-like method discussed in this video, so the only users who need worry are Linux (Android, Chrome OS) users and XNU/Darwin (iOS, macOS) users. As for embedded systems, well, that’s where most of the issues arise. Luckily my 2017 Mirai, unlike the Prius example in this video, happens to actually be connected to the Internet whenever my phone is connected to it, allowing the car itself to get software updates, so perhaps that’s a solution that car manufacturers can adopt in other cases.

kennystrawnmusic
Автор

I believe you meant to say "signed" and "unsigned" rather than "assigned" and "unassigned".

Wallawallawallawalla
Автор

Bro that's not 2 TRILLION (2, 147, 483, 647) That's 2 Billion (but you got the second part right by calling it 147 million)

shaunwilliamson