Standards shouldn't be behind a paywall

Top post of the hour is about an RFC from >20 years ago.

This is worse than the Linux stuff.

Y'all a bunch of nerds

A space is more problematic than a T tho

You've just become the nemesis of the entire unix-like userbase for praising the space.

allows a space instead of a T

That's a bug not a feature

Its funny because everything about ISO 8601 is covered on its Wikipedia article. Very few people need to spend the francs to need the spec.

The difference:

2023-12-12T21:18Z is ISO 8601 format

2023-12-12 21:18 is RFC 3339 Format

A small change

Yeah I like a girl who is firm on her choice of date time format....😂😂😂😂

I don’t even know what ISO 8601 is, but I agree with the sentiment

Well, they cover very different formats: https://pbs.twimg.com/media/FdzPYu-UAAADHEq.jpg

Relevant XKCD: https://xkcd.com/1179/

wtf does this even mean?

How could it be paywalled? I've never heard of anyone paying ISO to be able to write the date and time in a handy way.

We need a better one....

Ymd-ymd-yhms-yhms

Much clearer and easier for programmers.

RFC2795, because the IETF guys work hard, and then play hard on April fools.

iSO

The space is SO MUCH BETTER

RFC allows a space instead of a T (e.g. 2020-12-09 16:09:…) which is nicer to read.

That is the case for ISO 8601 as well though:

So a time might appear as either "T134730" in the basic format or "T13:47:30" in the extended format. ISO 8601-1:2019 allows the T to be omitted in the extended format, as in "13:47:30", but only allows the T to be omitted in the basic format when there is no risk of confusion with date expressions.

I don't get this one.