Current Events > It annoys me when people act like y2k was a non issue

(+) Yeah! (+)

It was overplayed a bit in the media, but it was actually a pretty massive issue, and if it hadn't been caught there would've actually been a lot of problems.

what a weird thing to be annoyed by

That was over twenty years ago, it's time to let it go

---

If this pandemic has taught me anything, it's that people will act like anything is a "huge, overblown" issue.

---

It legitimately caused plenty of problems but the world's infrastructure didn't crumble.

Remember when people though the world was going to end in 2012? Same stupid hype.

---

Wii_Shaker posted...

It legitimately caused plenty of problems but the world's infrastructure didn't crumble.

Remember when people though the world was going to end in 2012? Same stupid hype.

That was nonsense based on the Mayan calendar. Y2K was a real problem and it ended up feeling overblown because engineers fixed it ahead of time.

January 19 2038 is a much more serious problem and no one has any good solutions for it.

---

Wii_Shaker posted...

It legitimately caused plenty of problems but the world's infrastructure didn't crumble.

Remember when people though the world was going to end in 2012? Same stupid hype.

Infrastructure didn't crumble because Y2K became a big deal and things got fixed in time. Without that level of attention it likely would've been much worse.

Tyranthraxus posted...

That was nonsense based on the Mayan calendar. Y2K was a real problem and it ended up feeling overblown because engineers fixed it ahead of time.

January 19 2038 is a much more serious problem and no one has any good solutions for it.

I've heard of that, remind me what the issue is again?

RadiantJoyrock posted...

I've heard of that, remind me what the issue is again?

The Unix epoch overflows on that date resulting in a mix of undefined behavior and thinking that it's January 1, 1970.

There is no fix that is fully backwards compatible. Some people might have to accept that some legacy software just straight up won't work ever again.

---

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

---

Tyranthraxus posted...

January 19 2038 is a much more serious problem and no one has any good solutions for it.

Its already been solved.

https://www.forbes.com/sites/barrycollins/2020/10/19/relax-the-computing-world-wont-end-in-2038-but-2486-is-looking-grim/

Y2Js debut was definitely a huge deal

---

GregShmedley posted...

I do feel like 2012 was like the beginning of a new era that has resulted on a steady decline. Maybe it's the smartphones. I dunno.

Honestly, I agree, that was right around the time Obama triggered Putin and Trump started seriously thinking about running.

---

You weren't even alive back then, let it go lol

---

I had a Windows 3.1 computer that would go back to 1900 when you tried to set the clock to 2000

My Dad was teaching computer science during Y2K. He explained the problem to me but that it was an easy programming fix. We went on vacation.

---

Irony posted...

You weren't even alive back then, let it go lol

I was 14 in 99.....

modena posted...

My Dad was teaching computer science during Y2K. He explained the problem to me but that it was an easy programming fix. We went on vacation.

Easy enough except for the sheer scale of what needed adjustment.

Tyranthraxus posted...

There is no fix that is fully backwards compatible. Some people might have to accept that some legacy software just straight up won't work ever again.

Time to finally update that inventory software that's been running in COBOL since 1977.

RadiantJoyrock posted...

Easy enough except for the sheer scale of what needed adjustment.

That's true too.

---

Has the "4 December 292277026596 problem" been solved yet?

Questionmarktarius posted...

Time to finally update that inventory software that's been running in COBOL since 1977.

More like people still using lotus notes but I have no sympathy for people using lotus notes.

---