• Trantarius@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    11 months ago

    Y2K specifically makes no sense though. Any reasonable way of storing a year would use a binary integer of some length (especially when you want to use as little memory as possible). The same goes for manipulations; they are faster, more memory efficient, and easier to implement in binary. With an 8-bit signed integer counting from 1900, the concerning overflows would occur in 2028, not 2000. A base 10 representation would require at least 8 bits to store a two digit number anyway. There is no advantage to a base 10 representation, and there never has been. For Y2K to have been anything more significant than a text formatting issue, a whole lot of programmers would have had to go out of their way to be really, really bad at their jobs. Also, usage of dates beyond 2000 would have increased gradually for decades leading up to it, so the idea it would be any sort of sudden catastrophe is absurd.

    • SkippingRelax@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      a whole lot of programmers would have had to go out of their way to be really, really bad at their jobs.

      You don’t spend much time around them, do you?

    • The Octonaut@mander.xyz
      link
      fedilink
      English
      arrow-up
      0
      ·
      11 months ago

      The issue wasn’t using the dates. The issue was the computer believing it was now on those dates.

      I’m going to assume you aren’t old enough to remember, but the “only two digits to represent the year” issue predates computers. Lots of paper forms just gave two digits. And a lot of early computer work was just digitising paper forms.