you are viewing a single comment's thread
view the rest of the comments
[–] 113 points 5 months ago (13 children)

An insane amount of money and overtime went into changing software and data to make sure that a lot of bad things did not happen. It's not that the Y2K bug was a nothing burger, a lot of people worked very hard to make sure critical systems were changed.

  • source
  • hideshow 13 child comments
  • [–] 30 points 5 months ago (5 children)

    Yep, now we have the 2038 year coming for Linux. It already got me, I didnt want to renew my home NAS certificate every year, so I thought I'd do a 30 year cert. Well after 2038 it rolled the date to the 1960s...

  • source
  • parent
  • hideshow 5 child comments
  • [–] 11 points 5 months ago* (2 children)

    Debian is ready - as of Debian Trixie (released in August 2025), all software in the official repo is being compiled with 64-bit time. https://wiki.debian.org/ReleaseGoals/64bit-time

    For your home NAS, I'd recommend using Let's Encrypt with Certbot. You can use it for internal systems, as long as you have a real domain name. Use DNS verification instead of HTTP.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 months ago (1 child)

    So when some Linux apostle is preaching how I need the salvation of Linux in my life, I'll just tell them that I'm waiting for 2038, and then I'll jump in AFTER the apocalypse.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 5 months ago

    Join now lest ye not be saved. 😀 32 bit time keeping is the issue, most systems are 64 bit now, so its just logistics / implementation issue now, not a technology problem

  • source
  • parent
  • [–] 25 points 5 months ago

    I have been telling people this for 26 years now to no avail. I wish I hadn't busted my ass now so all the motherfuckers since then who claimed IT is useless could eat the giant dick of downtime.

  • source
  • parent
  • [–] 8 points 5 months ago

    And it's tough to remember just how fast computing was changing in the '90s, improving by leaps and bounds all the time with seemingly no ceiling in sight. Consumer computing power was doubling every one and a half years. And in, say, 1994 it wasn't unreasonable at all to assume that all of that crusty old tech from the '80s and even early '90s surely would have been replaced by the year 2000 anyway without anyone having to do anything special about it. Probably more than once... right?

    The crucial disconnect there was that tech people are not necessarily business people and I think a lot of folks grossly underestimated management's recalcitrance in spending money until it was more than clear they were facing a crisis.

  • source
  • parent
  • [–] 5 points 5 months ago (2 children)

    A lot of stupid businesses and government entities waited until the last fucking second to fix a problem they knew about for half a century.

    The overtime should have been exponential for them kicking the can down the road for literal generations.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 5 months ago

    We haven't changed. Companies will not spend more than they have to on IT if they think they can deal with it until next quarter. This was no different, plus developers of software didn't expect their stuff to become legacy and not updated with better programs. Memory was premium, so a few less bytes here and there that would work fine for a few years was what they did.

  • source
  • parent
  • [–] 2 points 5 months ago

    Half a century is a bit of a stretch, but I otherwise agree. It should not have gotten to the level of trouble it became, but I also dislike the implication in the OP that it was just a non-issue meant to scare people; it was a problem that indeed came to a head because many companies kicked the proverbial can, but a potential real problem nonetheless (especially in medical/insurance/monetary systems rather than "planes will rain from the sky" sorts of issues).

  • source
  • parent