You don't have to wait that long. Programmers are already patching software for the Y2K38.
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.
*Cries in industrial controller*
2147483647 + 1 will also be a rough year for humanity (or whatever is left)
People have been working for decades to fix the 2038 problem, so I don't think there's too much to worry about.
"Fuckin' Y10K..."
Yeah assuming tech gets that far before imploding
Every NHP instantly unshackles at midnight.
No moon is safe.
Programmers in 292,271,023,045 after uint64_t isn't enough for the unix timestamp anymore:
I don't think 10000 year is a problem. There is a real "year 2038 problem" that affects system storing unix time in signed int32, but it's mostly solved already. The next problem will be in year 33000 or something like that.
There are so many problems there is an entire Wikipedia page dedicated to them.
Well, I looked at a Year 10000 problem less than 2 hours ago. We're parsing logs to extract the timestamp and for that, we're using a regex which starts with:
\d{4}-\d{2}-\d{2}
So, we assume there to be 4 digits for the year, always. Can't use it, if you live in the year 10000 and beyond, nor in the year 999 and before.
There might be a new calendar year system by then. Probably some galactic dictator who says that the beginning of their rule is now Year Zero.
Year Zero of the Glorious Zorg Empire!
Good news! We'll be exctinct long before this happens. One less thing to worry about!
Y10K.
In 9999, this meme will be problematic because it assumes the entire galaxy conforms to an Earth-based calendar system.
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
oh just start at 0000 again, signate that as 10,000. Files didn't start until like 1979 anyways, and there can't be many left, and even if it is a problem, now you have 2000 years to not worry about it.
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).
Edit: the image in the OP is also a depiction of me reading replies. I just can't even.
I first heard about the Y2K bug in about 1993 from a programmer who was working on updating systems. These were all older systems, often written in COBOL, which did not use epoch time, and in fact didn't reference system time at all. They'd be doing math on data entered by users, and since they were written back when every byte of memory was precious (and nobody expected that the program would still be in use after 30 years), they'd be doing math on two-digit years. It would certainly be a problem to calculate people's ages, loan terms, payments due, et cetera, and get negative numbers.
Heck, I remember reading a story about a government system once that marked the residents of Hartford, CT as dead, because somehow the last letter of the city name data overflowed into the next column, and marked them as 'd'eceased. Y2K was definitely a real problem.
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.
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 they would have never done it.
Fun fact, lots of VW modules think it's August of 2094 for some reason.
We’re being short-sighted
Tell that to the billionaires speed-running terraforming this planet into a barren wasteland.
The two most difficult things in programming; dealing with time, naming things, and boundary conditions.
dealing with time
Network engineer here, it's just as bad here. Currently trying to figure out what to do with 'gaining' a negative leap second. In 2025, we may lose one for the first time in digital history.
Do you not have NTP?
I forgot what the N stands for in NTP, but the network engineer might know.
Nnni!
Absolutely. I'm a ddi engineer. NTP plays a huge part in my work. Systems, including ntp, are designed to handle leap seconds. Negative leap seconds are uncharted territory. I could go off on a long rant about it, but I doubt people care that much. It's really dry stuff.
I'll listen, then I can seem knowledgeable af when it gets mentioned on a call 3 days before it happens and everyone else is freaking out.
We love long dry niche rants though.
Time I can deal with, timezones however, fuck that shit all to hell.
Insert that Numberphile video with Tom Scott being reasonably angry at time zones.
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.