We're being short-sighted
-
[email protected]replied to [email protected] last edited by
Jibes, not jives.
If you're jiving, you're dancing.
-
30 years is very different than 8000 lol.
-
Insert that Numberphile video with Tom Scott being reasonably angry at time zones.
-
[email protected]replied to [email protected] last edited by
Fun fact, lots of VW modules think it's August of 2094 for some reason.
-
Gotta remember to use the proper time. Sometimes that's not proper time!
-
Possibly linuxreplied to [email protected] last edited by
Do you not have NTP?
-
[email protected]replied to [email protected] last edited by
Thanks for the correction, I didn't know that!
-
[email protected]replied to [email protected] last edited by
Not a storage problem but still a possible problem in UIs and niche date manipulations that assume years have 4 digits or 4 characters.
-
[email protected]replied to [email protected] last edited by
Y2k9 sounds like a problem that only affects calculations done in dog years.
-
I think it affects amd64 / x64 because they originally used a 32-bit time_t for compatibility with x86 to make multiarch easier.
I don't believe it affects arm64.
-
[email protected]replied to The Picard Maneuver last edited by
Every NHP instantly unshackles at midnight.
No moon is safe.
-
*Cries in industrial controller*
-
[email protected]replied to [email protected] last edited by
People have been working for decades to fix the 2038 problem, so I don't think there's too much to worry about.
-
[email protected]replied to Possibly linux last edited by
I forgot what the N stands for in NTP, but the network engineer might know.
-
đ° đ đą đĻ đŗ đĻ đ° âšī¸replied to The Picard Maneuver last edited by
"Fuckin' Y10K..."
-
[email protected]replied to [email protected] last edited by
This would be a great short story if for some reason the AI didn't realize there was going to be a date issue and didn't properly update itself causing it to crash. Then the problem is it was self sufficient for so long no humans know how to restart it or fix the issue, causing society to have a technology blackout for the first time in centuries.
-
[email protected]replied to [email protected] last edited by
Yes, it's kind of a familiar sci-fi trope - a supercomputer that has no built-in recovery mechanism in spite of being vitally important. Like the Star Trek episode where they made smoke come out of a robot's head by saying illogical things.
-
[email protected]replied to The Picard Maneuver last edited by
Yeah assuming tech gets that far before imploding
-
[email protected]replied to Possibly linux last edited by
Absolutely. I'm a ddi engineer. Infoblox. Systems, including ntp, are designed to handle leap seconds. Negative leap seconds are uncharted territory.
-
[email protected]replied to [email protected] last edited by
We love long dry niche rants though.