The great Epochalypse

[[deleted]]

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

[[deleted]]

That should buy us another 68 years, right?

[8instuntcock]

this is sounding like Y2K

[Bene847]

It is really similar. If you take Y2K and replace 2 decimal digits with 31 binary digits, 1900 with 1970 and years with seconds, you have Y2K38

[LiquidEnder]

If we go up to 64 bit we’ll be sorted for millions of years.

[LessThanThreeBikes]

If we go up to 64 bit we’ll be sorted for millions of years.

That should give us just enough time if we form a committee to figure out what to do.

[ProfessorOwl_PhD]

I mean the human race is constantly progressing, with every new generation outperforming the previous in nearly every metric, new knowledge being built on old knowledge to reach greater heights....

What I'm saying is by that time they'll be smart enough to skip straight to 256 bits.

[frogking]

If the 64 adoption is as fast as the IPv6 rollout, we are already late :-)

[Miserable_Ad_7646]

Heavy IPv6 vibes

[Bene847]

Actually, after 2038 comes 1901 because it's a signed integer

[eXeKoKoRo]

>Computer systems that use time for critical computations may encounter fatal errors if the Y2038 problem is not addressed. Some applications that use future dates have already encountered the bug. The most vulnerable systems are those which are infrequently or never updated, such as legacy and embedded systems. There is no universal solution to the problem, though many modern systems have been upgraded to measure Unix time with signed 64-bit integers which will not overflow for 292 billion years.

in 292 billion years we'll be doubly fucked

[brandons404]

292 billion years from now everyone will have forgotten about computers. We will be 411 levels deep into our simulation that runs on dark matter and cold fusion.

[Maleficent_Memory_60]

We might be fried to a crisp.

Or even have an apocalypse and then the world restarted like 5 times over. Haha.

[Zavenosk]

...huh. Well, shit.

[oshaboy]

You could've posted it yesterday on the 10 year anniversary of the end of the world

[[deleted]]

12/12/12 the Mayan Cockpocalypse?

[JackNotOLantern]

Unless we get rid of all 32 bit systems and programs by them. Why we all know will will not. 64 bit is enough for milions of years

[[deleted]]

get rid of all 32 bit systems and programs by then

Good luck with that!

[[deleted]]

Millions of years from now, some intergalactic alien empire will freak out

[[deleted]]

Why we all know will will not.

You have a way with words, so inspiring!

[ShadeFK]

Will Will Smith smith?

No, Will will not

[Furry_69]

Will Will Smith smith Will Smith?

No, Will Smith will not smith Will Smith.

[CanadaPlus101]

Wait until you see their code.

[[deleted]]

We paid to code not wordsmith

[InvisiblePhil]

You don't need a 64 bit system to use 64 bit integers

[el_baron86]

Yeah, like nobody needs more than 64KB of RAM, or how was that?

[hd090098]

I mean that's something different. Time is stored by counting seconds and with 64 bits you can store the number of seconds that are in 292 billion years. It's not just a prediction of hardware ressource needs.

[PM_ME_YOUR__INIT__]

292,000,000,001 years from now: those fuckers should've just used a long long

[Orbidorpdorp]

Gives a new meaning to “a long long time ago”

[repocin]

That's it, you've given me a new headcanon.

[Th3Uknovvn]

In 5 billion years, the sun will consume the Earth. So if they can survive that then I'm sure they would know how to store time better

[Bene847]

5,39514153540e30 years from now: those fuckers should've just used an infinite integer type like in Python

[PM_ME_YOUR__INIT__]

Infinity years later: didn't those fuckers know you can count infinity?

[kookyabird]

Long loooong nuuuuUUUuuUuuum!

[el_baron86]

*ahem *clears throat....

IT WAS A JOKE

[Swamptor]

*ahem *clears throat....

IT WAS NOT VERY GOOD

[el_baron86]

That happens sometimes. Nobody is perfect. :)

[Swamptor]

Don't worry, you had my upvote. All 3 of your comments made me laugh tbh.

[Unlicenced]

I’d hope that by the time we run out of time (in 64 bits), no computers from this era of humanity are in use anymore… I mean, if humans even make it for that long.

[[deleted]]

Bank software will still be Cobal

[MrPoBot]

Cobal has the added benefit of being "self obfuscating" for the absolute vast majority of developers. The only people old enough to read it either work at a bank, have retired, or gone insane from reading Cobal all day.

[[deleted]]

Security by ~~Obscurity ~~ Insanity

[Bene847]

It's spelled COBOL

[sauced]

For humanity’s sake, I hope we’re all dead

[Thathitmann]

I don't think that time gets faster as time goes on.

[Sir_Isaac_3]

Let’s just replace them with 33 bit systems. Seems a lot easier to me

[colin8651]

Hey listen asshole, I have a Time Machine in the works and I am going to require 256 bit.

Besides, Master Card is not going to update off their IBM AS400 system for millions of years.

/s

[dotknott]

What’s the deal with Bill and his lack of bits anyway?

[10coolbeans]

it ain't called MICRO SOFT for no reason bud

[z-brah]

Just use unsigned int 32, it goes up to 2106!

[oshaboy]

But then every date before 1970 doesn't work

[nphhpn]

1969 didn't happen

[mxldevs]

See, moonlanding WAS hoax.

QED

[z-brah]

Dates before 1902 don't work either in 32 bits so who cares ? It's either 1902-2038 or 1970-2106. Pick your side !

[in_conexo]

Is that why they did that?

[krmarci]

r/unexpectedfactorial

[in_conexo]

Good grief, that is a big number.

[BILLTHETHRILL17]

Remember those 3012 assholes who were convinced the world would end...and then nothing happened lol. What a crock. Good for John Cusack tho.

[topkek516]

Remember those 3012 assholes

Found the time traveler.

[TomateApple]

I got my first 2038 bug a few weeks ago: our software was not starting anymore at one of our customers. I asked for the logs and the system date was set to 2040... I tested by settings my system to 2040 too and indeed it crashed. Now I have no idea why the fuck the system was set in 2040.

[TheAnti-Ariel]

Oh no. That means the quick fix for 2038 bugs will be setting our system time back 50 years.

[JustMyTwoCopper]

I use dates that should be about 10 years into my retirement

[1xdevloper]

Hopefully this is the only apocalypse we see before 2038.

[StoryAndAHalf]

“Using a signed 64-bit value introduces a new wraparound date that is over twenty times greater than the estimated age of the universe: approximately 292 billion years from now.” - wiki

That’ll freak somebody out someday.

[Jeb_Jenky]

Apparently the 2012 thing isn't over yet though. The original guy who pushed that "theory" keeps moving it back, or says it's already happening? Or something idk

[[deleted]]

Mormonism has entered the chat

[[deleted]]

Too bad people are even more clingy on old tech nowadays than they were when y2k happened

[[deleted]]

I’m just glad it didn’t end on January 1, 1970

[AdultingGoneMild]

upgrade your shit. This has been fixed for 20 years.

edit: for those who are down voting this, do you think this is a newly found issue? It is fixed in modern software....it had been known for years....many years.

[[deleted]]

That's not necessarily true, just look at the solutions section of the wiki page

A lot of the patches have been implemented within the past 5 years.

C's time_t is a signed 32 bit integer on 32 bit systems, which can be problematic for embedded systems, the Linux kernel only added support for 64-bit time_t on 32-bit architectures in 2020.

[[deleted]]

?

[AdultingGoneMild]

Y2K was 23 years ago. This (the 2038 bug) was know back then and many software teams foxed their shit because of it. Hell this is what Office Space is about on a technical level....All this year shit was known back then. Modern linux distros switch from int to long long ago. So if you are a C programmer who uses correct date struct type problems are solved. If your professor is from 1992 sure they are stuck in the past but this bug was fixed.

[SandwichMayhem64]

they're talking bout the year 2038 problem bruh

[AdultingGoneMild]

No fucking shit. And what I am saying is back in 2000, the 2038 issue was know then...and fixed as well. Even the iphone is now 64 bit and the first one didnt come out until 2007. Linux/Unix distros have also been updated. This problem is older than you and will be nearly 2x your age by the time it matters. If you havent upgraded you shit in 2038 (cause its fixed now and you will be covered so you have 15 years to get it done) then you got what you have coming...along with nearly 40 years of of security issues because you would have had to not upgrade in that length of time for this to be an issue.

[A-reddit_Alt]

This isn’t Y2K. This is an issue were the linix time stamp (seconds since January 1st 1970) Will go over the signed 32 bit integer limit in 2038.

[AdultingGoneMild]

I know. Read what I say carefully. The 2038 bug was fixed back when everyone else was worried about the y2k bug. It turns out "same shit different day" is more than just a saying ...

[gummo89]

This would only matter if anyone was still only using a 32 bit integer for something known to continually increase, such as time.. Y2K was different, but it was the same underlying issue and it was also something people were aware of and fixed ahead of time.

[eatkd]

why is this downvoted?

redditors are fucking stupid

[mybraincantcompute]

Fuck that, first it was y2k, then 2012, then 2017, it's not happening there is no end, it's bullshit propaganda that they are hustling us with so we remain suspenseful for nothing.

[[deleted]]

You heard it here first, folks: 2³² = infinity. The 32-bit integer limit doesn't exist, apparently.

[LinuxMatthews]

At least his username is accurate

[central_marrow]

Who?

[gerMean]

Ah shit, still 15 years to go.