We're being short-sighted

[email protected]

Y2k9 sounds like a problem that only affects calculations done in dog years.

[email protected]

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]

Every NHP instantly unshackles at midnight.

No moon is safe.

Nomecks

*Cries in industrial controller*

[email protected]

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]

I forgot what the N stands for in NTP, but the network engineer might know.

🇰 🌀 🇱 🇦 🇳 🇦 🇰 ℹ️

"Fuckin' Y10K..."

[email protected]

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]

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]

Yeah assuming tech gets that far before imploding

[email protected]

Absolutely. I'm a ddi engineer. Infoblox. Systems, including ntp, are designed to handle leap seconds. Negative leap seconds are uncharted territory.

[email protected]

We love long dry niche rants though.

[email protected]

Maybe, but there are still a lot of invisible people involved to get the food all the way to your table. And small suppliers cannot afford to switch their whole operation to robots.

[email protected]

Yeah so they go out of business lol

[email protected]

Ditto for the Y6239 problem for what must be a dozen of pieces of software that use the hebrew calendar, when it switches to five digit years.