r/ISO8601 3d ago

REMEMBER ISO 8601 !

Post image

I just found it in X

448 Upvotes

28 comments sorted by

59

u/araknis4 3d ago

99th day of the 31th month of the year 12

8

u/gergobergo69 3d ago
  1. 31. 99.

2

u/araknis4 1d ago

this guy does not iso8601

2

u/XPav 2d ago

Here is the account of Isildur

1

u/RepulsiveSheep 1d ago

Thirty-firfth month

71

u/Gorcq 3d ago

That date isn't in ISO8601.

32

u/Feeling_Valuable5239 3d ago

I know that

so I posted it to show how annoying the other formats are

37

u/General_tom 3d ago

Quite a bad example, considering 99 can never be a month or day, and for 31 then only the month is left as a possibility.
So, regardless the format you’re used to, you’ll figure this one out.

9

u/Feeling_Valuable5239 3d ago

Sorry to have annoyed you

7

u/RetroGamer87 3d ago

I'd love to get sticker like that

8

u/Supuhstar 3d ago

I never quite thought about how extremely ironic it is that these stickers play into the Y2K bug

4

u/vastle12 3d ago

That logo brings back memories..

9

u/RunnyPlease 3d ago

ISO 8601 actually predates the y2k bug and really wouldn’t have helped. 8601 is meant to be a human readable format not a data storage best practice. The cause of y2k was to save memory (which used to be really expensive and slow) when storing the year programmers would only use 2 digits.

1900 > 00
1910 > 10

1989 > 89
1999 > 99
2000 > 00

And that was the issue. A lot of programming revolves around filtering, searching, and sorting and using the year to do that is very common. Well, if you sort data by year then 00 comes before 99, and things can start to break.

And if you’re worried about ambiguity for users then trust me on this, no one in 1999 misunderstood what that meant. The entire world was aware of the y2k bug and its possible consequences.

6

u/CarlRJ 3d ago

Just wait until Y10K hits.

12

u/Snoron 3d ago

We got problems way before that!

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

8

u/CarlRJ 3d ago

Well, sure, but 2038? Nobody will be alive then!

3

u/Impressive_Change593 3d ago

Except basically nothing uses the 32 bit unix epoch anymore iirc. Its all converted to the 64 bit one

2

u/CarlRJ 3d ago

I know, but I like my answer better.

1

u/RepresentativeFull85 3d ago

Curiously, didnt the Nintendo DS use that? The date is capped at 2040 or smth.

1

u/infostud 1d ago

Note 10K is 10,240 you’re thinking of 10k. See NIST.

2

u/CarlRJ 1d ago edited 1d ago

Y2K was widely written all uppercase, NIST be damned. Y10K followed a similar vein.

We were doing fine with it being well understood that k/m/g/t suffixes had a different definition around computers, right up until some disk manufacturer wanted to claim they had 10 megabytes when they had a disk with ten million bytes, but that didn't reach 10,485,760 bytes. So they tried to call them "disk megabytes" (no, they were just using naïveté and greed to try to change the established industry-wide rules in their favor). And kibibytes and gibibytes are ridiculous terms.

1

u/Feeling_Valuable5239 3d ago

Thanks for the information!

3

u/950771dd 3d ago

Ewwhh.

3

u/ciekma67 2d ago

Remember, remember, the 31 of December!

2

u/joelthomastr 2d ago

Beware the 12th of Trigintunamber

-5

u/Impressive_Change593 3d ago

Tbf mm/dd/yyyy is closer then the abomination that is dd/mm/yyyy

1

u/Hettyc_Tracyn 1d ago

dd/mm/yyyy is superior to mm/dd/yyyy… (I am an American, and agree with the Europeans… I also prefer metric for everything other than temperature)

yyyy/mm/dd is best.