The Devastating Year 2038 Bug 💻🐞

[@CodingWithLewis]

This isn't an April Fools joke! Sorry for the confusion everyone 😅

[@creammando]

Wrong time to post lol

[@user-dp2su3of8g]

I thought what the heck with this 2038 Year when I first heard.

[@justindoplayer1516]

This video reminding me of John titor

[@opinion_panda]

Man y’all remember y2k?

[@Rage57350]

So just like Y2K. I was in the guards and on call for this. I remember them making a big stink of it. Made it sound like it was going to be the end of the world as we knew it, back to the stone age for us. woke up the next day and was so disappointed 😅

[@williamt83]

Plenty of time to fix. Which means we'll see the last patches come through on January 17 2038.

[@S_M44Z]

Or the first patch

[@wumwum42]

Thats what they thpught in Dont look up as well...So you defiently will be right.

[@SeaSerpentLevi]

More like the first beta 😂

[@frozeneye100]

I wonder if JP will patch the theoretical everyone in Japan being called Sato or this bug first. Let’s see which comes first. Bet both will end up dev>null

[@Craigs653]

Hahahaha ah nope, do you know haw many companies run on win 7 and xp
A crap ton
And they won't update due to them running expensive machines

[@tkwkV0]

Cannot wait to see "Y2.038K Ready" computers

[@Algeriawindows69]

Y2k38

[@tacokoneko]

your computer can only be affected by Y2038 if it is 32-bit and, *all 32-bit linux versions since 2019 are technically "Y2038 ready"* . so to avoid your old computer being affected all you have to do is use a new enough linux OS.

[@OculuKabak]

64bit already safe

[@DeathcageLMH]

"S.32B"

[@Algeriawindows69]

@@DeathcageLMH MMXXXVIII

[@DrajadKusumaAdiNewNormal]

"problem for somebody else to fix"
sounds legit

[@RealVoidex]

No one will be here when that happens

[@tihc1]

Oh btw it isn’t an April fools, he clarified that lol

[@yakumoyukari4405]

​@@RealVoidexeven the universe itself, unless... It actually explodes and dies repeatedly (which I hope it does)

[@polycrystallinecandy]

​@@yakumoyukari4405universe will probably be around then. Current estimates say the star formation phase will last >100 trillion years

[@yakumoyukari4405]

@@polycrystallinecandy ah thats great to hear because once I been told it has ~20 billion years to live

[@MTFISHER]

Someone 293 billion years from now: WTF BRO?!?

[@halko1]

They’ll be like ”WTF is 64 bit unix time and why didn’t they choose 256 bits?”

[@vincenthills5024]

They'll be like why tf did we not use 1KiB integer

[@ethereal41]

They'll probably have higher bit architecture at that time, pretty cool to think about.

[@polycrystallinecandy]

If we're still dealing classical computers with bits in 292,000,000,000 years, I'll be very disappointed. We are already building quantum computers. Classical to quantum in less than 100 years. They'll probably be a million steps ahead. Like forget DNA computing and molecular machines. They'll have pocket universes where they tuned the big bang just right to turn the entire universe into a computer

[@ThisShitWontWor]

⁠​⁠@@polycrystallinecandyanyway earth gonna be pwned by the sun in 1.75-3.25 billions years unless we found another planet in a new solar system and of course if the humanity doesn’t destroy itself before so 💀

[@CodingWithLewis]

I’ll wait till 2037 to deal with it

[@wvistalover]

Lol

[@floboyyt]

Same lol

[@Habibullah-pn7sj]

Thanks! 😊
I'll try using some HTML to give you a hand. 😂

[@Starry00wolf]

Python for me

[@bapt_andthebasses]

😢 way before 2038 we will have bigger issues.

[@JustPyroYT]

Fun fact: Windows Media Player is one of the Programs containing this bug.

[@SuperiorZeeko]

Even if addressed, every program will be bugged that assigned the current date to a variable that cannot go beyond 32bit like the Int data type in various languages. Or even “stricter” ones like “int32_t” in C.

[@flueritv]

​@@SuperiorZeeko but why didn't they use unsigned int? I mean it would give the double amount of time.

[@alexbleks]

Many databases around the world also use 32 bit for timekeeping / logging too

[@svenmify]

@@flueritvhabit. When you make a ton of code / databases, you often don’t stop to think about an overflow issue far in the future. You just make an int and move on to the next thing. Obviously not everybody, but enough people (including me, probably) have made this mistake

[@mgord9518]

​@@flueritvBecause Unix dates *shouldn't* be an unsigned int. You should be able to represent values pre-1970 even if you don't plan on using them. If you want more data, use a larger datatype.
Choosing to use an unsigned int when the standard for Unix time is signed, you're likely to come across issues converting timestamps, along with the fact that you aren't actually solving the problem, just pushing it out a few more decades.

[@AsianCurls]

Double it and give it to the next person

[@sheepriderkiller1181]

double is too less said here

[@hzmx727]

Thought this was April Fools joke but sounds like Y2K situation

[@bomberfish77]

It actually isn’t, but it only affects 32-bit computers.

[@tdrg_]

This a real thing

[@CodingWithLewis]

lol bad timing on my part 😅

[@jadedkaiju]

fr

[@SuperBro112Lol]

@@bomberfish77 i think no its gonna be at almost all computers (windows will be mostly ok because its no unix-like system)

[@R00kTruth]

it hasn't been an issue since they realised this in the 2000's...

[@touma-san91]

It's bit of mixed bag actually... Not every application has addressed it.

[@R00kTruth]

@@touma-san91 they wouldn't need to, they would use the os times/dates. but I get what you mean

[@jackoberto01]

​@@R00kTruthOf course they would need to if their specific implementation still relies on 32bit values. Not all applications uses the time from the OS.

[@No-day-off]

Yeah because they were in the 2000's not year 2037. Same is when it's due Monday and now it's friday night.

[@R00kTruth]

@@No-day-off what .. my comment meant, they've already fixed this issue. in other words this hasn't ever been an issue...

[@lua_programmer]

BRUH
if it were 2048
it'd be so much funnier to me.
I love the number 78

[@yesimstupid_]

me: *Sets time on pc to 2039*

[@znotchill]

@@cf8wuf98w4lu probably nothing because most devices are 64 bit now

[@MrAB-fo7zk]

Seriously doesn't matter how many bits your OS/processor is. Keep seeing this. It doesn't matter much. In a 64 bit operating system it will have the C type time_t or whatnot as a 64 bit integer because it's going to be pegged to a normal width int. But databases and tons of applications don't use that type alias plus the other infinite situations. The issue is going to be present anywhere a Unix timestamp is stored in a 32 bit integer which can be anywhere.

[@MersitonTheGood]

@@cf8wuf98w4luonly 32-bit apps like Windows Media Player Legacy will experience errors, nothing else.

[@codenocode]

we travelling back in time with this one boys 🗣️

[@vpansf]

“Remember him?"
Y2K
“This is him now."
Y2K38
“Feel old yet?"

[@pmlstk]

All this means is that on January 2038, Y2J Chris Jericho will still another run at AEW champ

[@MCasterAnd]

oh my fucking god
I just KNOW that I will be dealing with absolute ancient IT in 2038 regarding this lmfao

[@badpiggies988]

I’ve set two time-capsule reminders for myself: One for the good ending the day after 1/1/38, and one for the bad ending on 12/13/1901- each with a pre-written message to my future self under “notes”.

[@jdotgururaj]

People: we got a bug, you gotta fix it to save humanity
Dev: pushes the bug into future for billion years
dev: its not my problem anymore☺️

[@FulcanelliRosetta]

Pretty sure that they have already discussed plans to abandon 32 entirely with exception to niche cases.

[@alex2143]

I know one thing for certain. I am not going to be on a plane, on a train or in a car when this happens. Fuck that. Imagine being in a moving vehicle with millions of computers, all of which are potentially going to suffer a computer bug all at the same time.

[@BigBrain05]

In 300 billion years I don't think computer not working will be a problem when there has not been a earth for hundreds of billionx of years since earth existed

[@gtbpr_00]

sounds a lot like the year 2000 thing

[@russianvideovlogguy]

This dude was clearly born after y2k 😂

[@PiotrPilinko]

y2k was not so common as 32bit time_t in unix API.

[@delvinciposterkid]

So that's why my Robco terminal posts a "date out of range" error.

[@masonhidari]

Bro is recreating the 2000 scare

[@beowolf9480]

Difference is, this one will actually happen

[@oceanbackwards1903]

we literally already went through this
everything will be fine

[@Minecraft-3699]

This has already been widely addressed, nothing to worry about

[@EzGaming69420]

This is Y2K all over again

[@gerardkinneen7252]

The millennium bug is back with a bang

[@locobob]

Y2K.38 just doesn’t roll off the tongue like Y2K does…

[@johncake1337]

Y2K 2: electric boogaloo

[@PhirePhlame]

I thought 64-bit timecodes were already in use? Though older OSes may still have the issue, which is with how high a number can climb while still existing in only 32 bits. System clocks are literally counting the number of seconds since the beginning moment of Jan 1, 1970.

[@shefket89]

Rhat sounds like year 2000 problem with win98

[@MyCodingDiary]

You make learning fun and easy. Kudos to you!

[@alistar3729]

Well imagine if they going to say "well let's go for 128 bit " 😂

[@AmCanTech]

Time for a new type: Triple precision floating point numbers 😂

[@Casper042]

3:14am is UTC
So for Americans it will be Late on the 18th
10:14pm for East Coast
7:14pm for West Coast

[@Roach18]

We federalizing Australia with this one

[@bigspicydad8970]

This computer bug could be devastating if we do not address it 💅

[@PiotrPilinko]

It is currently addressed, but a lot of embedded systems are currently not supported. So they might just stop working correctly.

[@alexbleks]

The universe has imploded within 200 billion years anyways

[@Toad573]

Bro is really time traveling forward from 1999.

[@breadanator]

bro knows even the seconds WOW.

[@toomnLP]

Y2K-Bug energy

[@andrewkvk1707]

Why did they bother signing the integer? What would be the application of representing time prior to the epoch in unix?

[@dfntlynotjorn]

So thats why when I compile C with meson it's always checking for 2038

[@kirbo5759]

You ever get deja vu?

[@Kira_x86_64]

I was so confused watching this from 7 days after April fools.

[@MyCodingDiary]

Your videos always make my day. Keep shining!

[@nidhu595]

This feels like a y2k reboot

[@PiotrPilinko]

But it affects much more devices than y2k problem. Especially embedded devices and some databases.

[@teateachimchim733]

bro tryna predict 2038 whilst were 2024
😂

[@cvrsemark9120]

Thinking about the 64-bit processors made me feel safe, considering this topic.

[@tPlayerioT]

"problem for somebody else to fix" 😂😂😂😂😂😂😂

[@mohsena4632]

This is an idea for a movie.

[@jackdavenport5011]

If you’re still using a 32 bit computer in 2038 you deserve to have it break lmao

[@geowhat]

why store it in a signed int? its not like time goes negative

[@abhishekmehandiratta4241]

It's termed as Epochalypse

[@Thunderstorm21081]

everywhere you cannot escape pi even Y2.038K is pi

[@zln3am]

Thats actually the most normal thing ever for us to already know we'll have old enough systems in place with this method in over a decate. Bet they'll be especially in place for important systems like airlines once they upgrade their tech

[@endcensorship874]

Dude, don't threaten me with a good time. You mean, we might need to go back to how it was in, say, 1984? Yes, please.

[@randomdude1053]

I think the biggest issue is from older systems that are used and not really updated for critical uses eg. Utilities and healthcare etc. 😊

[@YakobtoshiNakamoto]

ATM’s are a big one. In the UK a lot of them are still running embedded Windows XP 😂

[@Tobsson]

Huh, I was actually thinking about this the other day. Probably add a starting byte to tell where to count from. Or transform it to 64 bit. Or both.

[@truckjumperdude]

Why would they use a signed integer? Negative time isn't necessary

[@tonightweride77]

Millennium 2000 flashback 😂

[@markcoren2842]

Lol been there, done that 25 years ago. This time around I get to kick back and watch 😜

[@eXzile81]

The same absurdity they claimed in 1999 to 2000, known as 'The millennium bug' it did fuck all.

[@_HetShah_]

Why did they used signed integer, when the hell time started to go in -ve

[@YNNVex]

Bro really tryna bring Y2K back🤡bro is tryna make people trip for nun

[@KatSun3i]

banking systems will hate implementing something new and complicated into legacy code lol, may a god or something be with them on that one, bc theyre gonna need it.

[@NatureSurfer]

Reminds me of the Y2K problem back in the day 😂

[@The_flipsideview]

The problem of integer overflow ia kind of common. It has happend in many popular programs like donkey kong, packman, it has even happened to an airplane company(i think boeing).

[@PubRunner]

The y2k bug was a marketing ploy as this will be.

[@jakob8940]

🤦

[@niklas9021]

Did people not think about this 54 years ago?? 😅 They really thought, armageddonwas a thing huh😂

[@PiotrPilinko]

Memory was expensive. CPUs were slower. 32bit for unix time seemed to be fine...

[@PS3PCDJ]

Who the hell decided to use signed integer for something only going up in the positive range?

[@gavrielamati9939]

Sounds like the millennium bug

[@DoingthingswithDAN]

I think the GPS reset has been annoying enough.. every Honda clock that ran on GPS is stuck 30 years back

[@ipadize]

donnt worry, some time in the next 292 billion years, we will use 128 bit systems

[@m0ke0]

"problem for someone else to fix" Not like they'll delay it again lil

[@scotthay9874]

My zx spectrum home computer will still be working. Bring back cassette tapes. lol.

[@lincsmash6795]

The same thing happened in the year 1999 with switching to 2000, nothing got destroyed.

[@PiotrPilinko]

Because a lot of money was put into fixing the problem before 2k occurred.

[@SS-gu2tx]

Can anyone name any critical devices that cannot count integers this high?

[@gwaptiva]

Can't wait to stock up my retirement with fixing this stuff, for a price

[@Bill_D.]

Just do what I did for Y2K, reset the year for an earlier time.

[@avonzo]

This is like the Y2K bug!

[@TheBurntHoney]

The problem is that most databases dont support u64 :(

[@SeinaruShi]

Why does a date need to be signed? Have it unsigned lmao

[@yigawaffle]

Remember all the fear of Y2K? And how, because we were ready, it didn't do _SH*T?_ Yeah, these two scenarios don't seem similar _at all._

[@PiotrPilinko]

They are similar, but Y2K took only 300 billions USD to fix most of the problems (over 550 billions in current value). y38 problem will be much more expensive to fix.

[@pizzadude007]

Something like this happened to my Samsung 3D Blu-ray a couple years ago

[@N3haaaa]

I'll panic in 2037 to Jan 18 2038.

[@arghjain1949]

Someone intentionally putted it, so that it can be fix later as to not loose job 😂

[@thenameisluk]

o no
anyway debian is already in process of switching to 64 version
lol

[@limo1795]

That would be cool as an easter egg

[@aeromaxout]

"affected by a bug that is unknown"...
Why not just set system clocks to that date in a closed lab and just see what happens?
Also, this is Y2K all over again.

[@DaltonKevinM]

Y2K again. What's the next "the time is near" computer date thing after this one?

[@ChippMcDippy]

Sounds like the Y2K bug scare haha

[@PiotrPilinko]

A lot of money was spend to fix almost all problems with Y2K. And in this case much more money will be spent to avoid problems.

[@ejsvegas5724]

ok so it's the Y2k bug all over again.

[@drakewarnock1239]

Oh god it's Y2K all over again.. The world is over! Planes are going to forget they were invented and fall out of the sky!
That was a real thing I heard back during Y2K.

[@lloricode]

Will mark this to my calendar, hope not to die sooner 😅😅😅

[@LaBAdochnicht]

Today in 292Billion years is gonna be hell 💀

[@nnnnwwww00]

So my PC will become a time machine in 14 years.

[@MrNiceGuy442]

they could fix it on the day before by the number of times that the operating systems are updated now a days

[@rrett44556]

IVE SEEN THAT NUMBER BEFORE! THATS MAX CASH IN RUNESCAPE!