We're being short-sighted

[email protected]

That's true until it isn't. Automation is on its way. Marching ever onward.

The factory I work in built a new building this year that employs 1/4 of the workers as the next newest one and does 2.5x the output.

Flax

Still set by London

[email protected]

Programmers dealing with the timezones of asymmetric period binary and trinary star systems once we go interstellar

BlanketsWithSmallpox

I'll let you in on a secret.

Humanity and the animals that we like will get through just fine.

Humans in general and the vast majority of biodiversity will be fucked.

[email protected]

just to nitpick, they said the "poorest", not the poor in general.
The poorest are the most vulnerable, and, I suppose, not absolutely crucial for the ruling class.

[email protected]

"Were being short-sighted"

Lol Picard maneuver. Pretty sure your opinion wasn't asked for.

[email protected]

I've been curious about that myself. On one hand, it still seems far away. On the other hand, it's a bit over 13 years away and I have gear actively in use that's older than that today.

[email protected]

Actual programmers wondering why this joke doesn't mention 65535...

[email protected]

More of a front end issue actually, almost all time is just stored as the number of seconds since 00:00:00 Jan 1 1970.

[email protected]

And it's represented as a 64 bits value, which is over 500 billions years.

[email protected]

and I think the ROC government in exhile in Taiwan stopped using it.

Actually it is still used. It's everywhere in legal documents, government documents and stuff. Though people more commonly say 2024 instead of 民國113年.

[email protected]

64 bits value

.... About that...
https://en.wikipedia.org/wiki/Year_2038_problem

[email protected]

That's the 32 bit timestamp

[email protected]

You still need loaders, drivers, retailers to get anything to the customer. A lot of rich ski and holiday towns can't staff the stores and Cafe's, because the employees can't afford to pay rent in the same towns

[email protected]

In this thread: mostly people that don't know how timekeeping works on computers.

This is already something that we're solving for. At this point, it's like 90% or better, ready to go.

See: https://en.m.wikipedia.org/wiki/Year_2038_problem

Time keeping, commonly, is stored as a binary number that represents how many seconds have passed since midnight (UTC) on January 1st 1970. Since the year 10,000 isn't x seconds away from epoch (1970-01-01T00:00:00Z), where x is any factor of 2 (aka 2^x, where x is any integer), any discrepancies in the use of "year" as a 4 digit number vs a 5 digit number, are entirely a display issue (front end). The thing that does the actual processing, storing and evaluation of time, gives absolutely no fucks about what "year" it is, because the current datetime is a binary number representing the seconds since epoch.

Whether that is displayed to you correctly or not, doesn't matter in the slightest. The machine will function even if you see some weird shit, like the year being 99 100 because some lazy person decided to hard code it to show "99" as the first two digits, then take the current year, subtract 9900, and display whatever was left (so it would show the year 9999 as "99", and the year 10000 as year "100") so the date becomes 99 concatenated with the last two (now three) digits left over.

I get that it's a joke, but the joke isn't based on any technical understanding of how timekeeping works in technology.

The whole W2k thing was a bunch of fear mongering horse shit. For most systems, the year would have shown as "19-100", 1900, or simply "00" (or some variant thereof).

[email protected]

We've still got time to fix it, and the next release of Debian will likely have a time-64 complete userland. I don't know the status of other "bedrock" distributions, but I expect that for all Linux (and BSD) systems that don't have to support a proprietary time-32 program, everything will be time-64 with nearly a decade to spare.

[email protected]

Except the shitty ones have more money and political power.

[email protected]

Nah, they will do what they always do. Change some system environmental variables to move the zero date on till after they would have retired.

Nobody wants to touch the original code, it was developed in the 1970s

[email protected]

My brother in Christ, there's more to time than just storing it. Every datetime library I've ever used only documents formatting/parsing support up to four year digits. If they suddenly also supported five digits, I guarantee it will lead to bugs in handling existing dates, as not all date formats could still be parsed unambiguously.

It won't help you if time is stored perfectly, while none of your applications support it.