We're being short-sighted
-
You know, this is ironic
-
I get your point, but in the same way that people "shouldn't" have been using two digits for year storage, there are certainly many parsers of ISO 8601 that don't match the spec. In 8,000 years I don't think this will be a problem though lol. I don't think we can really perceive what technology might be like that far in the future. But, hypothetically, is year 10,000 was in a few days and this was year 9,999 I would suspect we'd see at least some problems come January.
As an example, YAML 1.2 changed Boolean representation to only be case insensitive in 2009, but in [2022 people still complain about the 1.1 version]. (Caveat: I don't know if this person actually ran into a "real" problem or only a hypothetical one.)
-
I remember reading a primary source about someone's experience fixing Y2K stuff. I wish I could find it or remember more. The funniest part was that they actually got everything to work, but on January 1st when they tried to get into work their badge didn't work! The system on their badge reader was broken due to Y2K lol.
-
[email protected]replied to [email protected] last edited by
Time I can deal with, timezones however, fuck that shit all to hell.
-
[email protected]replied to The Picard Maneuver last edited by
2147483,647 + 1 will also be a rough year for humanity (or whatever is left)
-
[email protected]replied to [email protected] last edited by
dealing with time
Network engineer here, it's just as bad here. Currently trying to figure out what to do with 'gaining' a leap second.
-
[email protected]replied to [email protected] last edited by
Y2K wasn't entirely fear mongering horse shit. There were quite a few important cogs in our digital infrastructure that were using code that would not work past 1999. It was necessary to terrify corporate ownership into paying to fix the code, otherwise there would have never done it.
-
I mean, that's exactly what programmers in the '70s thought. That there would be no way in hell that their crap code would still be in use going onto 2000.
Thing is, copy/paste is always going to be easier than writing new code and that's only going to get worse as chat bots start coding for us.
-
[email protected]replied to The Picard Maneuver last edited by
You don't have to wait that long. Programmers are already patching software for the Y2K38.
-
[email protected]replied to [email protected] last edited by
Lmao I actively work with shortdates in a database because I have no control over how things are stored. They need to solve before 100 years have passed from the epoch, but at some point before then it'll be fun to figure out if "58" in a date of birth is 1958 or 2058.
-
"Fanatical" would be a word to use there maybe.
