• valkyre09@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    Y2K is one of those stories we look back on and think what a silly old load of nonsense. Truth is, if it wasn’t for the countless hours of overtime people put in to making those outdated systems support the date change, it really would have been utter carnage. You saw how crazy things got when we started to run low on toilet paper for a few weeks.

  • ritswd@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    No, it wasn’t like that. Remember that while computer technology was fairly mainstream, it wasn’t nearly as engrained into our lives as today. So people were talking about a worst-case scenario that involved technological things: potential power outages, administrations maybe shutting down, some public transportation maybe shutting down, … To me, it felt like people were getting ready for being potentially majorly inconvenienced, but that they weren’t at all freaking out.

    I do remember the first few days of January 2000 felt like a good fun joke. “All that for this!”

    • FuglyDuck@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      2 years ago

      most of the concern for Y2K was actually about old systems. keep in mind, the IRS, for example, still runs servers with COBOL on it today, as their main database. it works, and it’s reliable. They’re far from the only group (read: banks, government agencies, hospitals,) who still do so.

      those systems… they had no idea what would happen and had to figure something out. most programs at the time didn’t actually acount for the first two digits of the year. 1922 and 2022 would have been indiferentiable to those programs. for then-modern systems, it was a simple patch. For the old equipment… not so much…