3 ms·

I am a little confused here, the y2k bug at least followed some logic. But I am not following what about "2022" could have caused something like this in a few

• MegaDeKay 5y ago
  One of the comments from the linked article... things break if you write the date in this format to a 32 bit integer. "It hasn't been in the news much but yesterday the date was written by many computers as 2201010001 (YYMMDDHHMM). Many older computers that store the date this way cannot handle any number bigger than 2147483647, so as soon as the year began with a 22, it fails and can no longer register the date/time correctly."
  • BeefWellington 5y ago
    Importantly, a 32-bit signed integer. If this was using unsigned it would work until 2042.
    • gompertz 5y ago
      That's what makes it even more unfathomable how these bugs happen... Not only are they using the wrong data type, but they are using signed as well. Everytime I declare variables I think "will this ever be negative", so that I'm getting maximum value.
  • apeace 5y ago
    This makes sense, but I don't understand how it would self-correct in August? It seems like the integer will keep getting larger.