this post was submitted on 18 Dec 2024
1099 points (98.5% liked)

memes

10666 readers
1905 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to [email protected]

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/AdsNo advertisements or spam. This is an instance rule and the only way to live.

Sister communities

founded 2 years ago
MODERATORS
 
(page 3) 31 comments
sorted by: hot top controversial new old
[–] [email protected] 40 points 4 days ago (2 children)
load more comments (2 replies)
[–] [email protected] 47 points 4 days ago (1 children)

Good news! We'll be exctinct long before this happens. One less thing to worry about!

[–] [email protected] 14 points 4 days ago (1 children)

Seems hyperbolic to assume we will be extinct by 9999.

Sure we’re heading for a climate crisis, but I don’t think all humans will be dead; Just the poorest.

[–] [email protected] 32 points 4 days ago (6 children)

That has forever been the fallacy.

The poor won't die in the apocalypse leaving only the rich behind. The poor will die, and the rich will be faced with the harsh reality that they needed an army of poor working under them to sustain themselves, leading them to all die within the generation.

load more comments (6 replies)
[–] [email protected] 32 points 4 days ago (1 children)

In 9999, this meme will be problematic because it assumes the entire galaxy conforms to an Earth-based calendar system.

[–] [email protected] 15 points 4 days ago (1 children)

Well the USA is on Earth so obviously the earth calendar is the default.

load more comments (1 replies)
[–] [email protected] 17 points 4 days ago* (last edited 4 days ago)

Awww shit, time to rewatch my favourite Jike Mudge movie starring Lon Rivingston; Space Office (9999).

Haha, I can't believe this guy has the job of manually changing all the dates on the company's database, this place sucks. I bet the past was way better.

[–] [email protected] 4 points 4 days ago (1 children)

What about the year TREE(3)?

[–] [email protected] 3 points 4 days ago (1 children)

Ugh, I definitely don’t have the bandwidth to support anything beyond the year graham’s number.

[–] [email protected] 3 points 4 days ago

"How many years is that?"
"At least THIS many." (holds up 4 Knuth's arrow notations fingers)

[–] [email protected] 95 points 4 days ago (9 children)

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.

[–] [email protected] 3 points 4 days ago (4 children)
load more comments (4 replies)
[–] [email protected] 5 points 4 days ago

it’s mostly solved already

I wished I believe this. Or I guess I agree that it is solved in most software but there is lots of commonly used software where it isn't. One broken bit of software can fairly easily take down a whole site or OS.

Try to create an event in 2040 in your favourite calendar. There is a decent chance it isn't supported. I would say most calendar servers support it, but the frontends often don't or vice-versa.

[–] [email protected] 22 points 4 days ago (2 children)

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.

[–] [email protected] 12 points 4 days ago

Just start over at year 0000 AT (after ten thousand)

[–] [email protected] 6 points 4 days ago (1 children)

The ISO time standard will certainly need to be redone

[–] [email protected] 5 points 4 days ago (2 children)

Do you think so? Surely, it's able to handle dates before the year 999 correctly, so I'd also expect it to handle years beyond 10000. The \d{4} is just our bodged assumption, because well, I have actually never seen a log line with a year that wasn't 4 digits...

[–] [email protected] 8 points 4 days ago (1 children)

Kinda?

Each date and time value has a fixed number of digits that must be padded with leading zeros.

To represent years before 0000 or after 9999, the standard also permits the expansion of the year representation but only by prior agreement between the sender and the receiver.[21] An expanded year representation [±YYYYY] must have an agreed-upon number of extra year digits beyond the four-digit minimum, and it must be prefixed with a + or − sign[22] instead of the more common AD/BC (or CE/BCE) notation; by convention 1 BC is labelled +0000, 2 BC is labeled −0001, and so on.[23]

load more comments (1 replies)
[–] [email protected] 5 points 4 days ago

Luckily I'll be retired by then.

[–] [email protected] 7 points 4 days ago (1 children)

It's going to be significantly more than the year 33000 before we run out of 64-bit epoch timestamps.

The max value for signed 64-but epoch values is more than 292 billion years away, or 20 times the age of the universe itself.

So yeah, we're basically solid forever with 64-bit

load more comments (1 replies)
[–] [email protected] 51 points 4 days ago (2 children)

There are so many problems there is an entire Wikipedia page dedicated to them.

[–] [email protected] 2 points 4 days ago

I'm pretty certain most of my work inevitably ends up being related to a time issue

[–] [email protected] 14 points 4 days ago

Yes, there are random systems using every kind of smart or brain-dead option out there.

But the 2038 problem impacts the previous standard, and the current one will take ages to fail. (No, it's not 33000, unless you are using some variant of the standard that counts nanoseconds instead of seconds. Those usually have more bits nowadays, but some odd older systems do it on the same 64 bits from the standard.)

[–] [email protected] 12 points 4 days ago

It’s a UX problem rather than a date format problem at that point. Many form fields require exactly 4 digits.

load more comments (2 replies)
[–] [email protected] 56 points 4 days ago (2 children)

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!

[–] [email protected] 7 points 4 days ago (1 children)
[–] [email protected] 13 points 4 days ago (1 children)

Lol China used to use "Year 1" right after Xinhai Revolution.

Its "民国" (ROC) followed by the year number

Example: 民国一年 ROC Year One (aka 1912)

(ROC stand for Republic of China, btw)

Then the communists kicked the KMT out, and I think the ROC government in exhile in Taiwan stopped using it.

load more comments (1 replies)
[–] [email protected] 138 points 4 days ago (4 children)

Programmers in 292,271,023,045 after uint64_t isn't enough for the unix timestamp anymore:

[–] [email protected] 11 points 4 days ago (4 children)
load more comments (4 replies)
load more comments (3 replies)
load more comments
view more: ‹ prev next ›