• FuglyDuck
    link
    English
    85 months ago

    I’m getting Y2K vibes,

    • @jordanlundM
      link
      English
      165 months ago

      It’s funny you say that, because this scenario was how I explained it back in the day…

      Imagine the US comes out with a shiny new quarter, it’s super cool, but won’t fit in any existing coin slot.

      Upgrading one machine isn’t too bad if you know what you’re doing, but then doing every machine on a block, or a street, or a city, or a state? Suddenly way more complicated.

      Oh, and they ALL have to be done by a specific date.

      • FuglyDuck
        link
        English
        155 months ago

        my dad was a UNIX sysadmin. His assertion- at the time- that we’d be fine, did not live up the vast amounts of overtime he put in in during '99.

        (To be clear it was never the then-modern systems, like windows ME, or '95 that were at problem. it was all the old-as fuck stuff… every major institution still uses. Like IRS’s COBOL database… that’s… still being…used.all of that stuff, they needed to patch to make it okay.)

        • @TexasDrunk
          link
          English
          185 months ago

          Just wait until 2038. More overtime!

          • FuglyDuck
            link
            English
            9
            edit-2
            5 months ago

            he just retired this year!

            (so… uh… what happens in 2038?) (edit… I’ll worry about 2038 if we actually get to 2030.)

            • @Serinus
              link
              English
              225 months ago

              Unix time starts January 1st, 1970 and counts the number of seconds since then.

              Right now it is 1718265480 (approximately).

              That’s stored in a 32 bit signed integer. It hits max int in January of 2038.

              Unix timestamp gif of rolling over in 2038

            • @Archer
              link
              English
              105 months ago

              UNIX epoch limit. Date goes back to 1970