Perfect date
-
This post did not contain any content.
Heretic!
YYYY.MM.DD is the correct format.
-
This post did not contain any content.
This is stupid AF.
YYYY/MM/DD
This is the best choice.
-
For computing or sorting purposes, YYYY-MM-DD is best. But in day to day writing a date, I prefer DD-MON-YYYY.
I'm sorry that you're wrong... What a bummer.
-
ISO 8601 is clearly much superior due to being delimited.
ISO is paywalled therefore inferior than the free RFC.
-
I mean slashes
/instead of colons.That’s not a colon. Both are commonly in use in Europe. USA just switched the d/m
-
This post did not contain any content.
l jS F Y
-
YYYYMMDDHHMMSS is the only acceptable format.
Nope, it clearly should be mmsshhMMDDYYYY
-
This post did not contain any content.
For consistency, Americans should adopt mm:ss.hh MM-DD-YYYY.
-
If you use DD/MM/YYYY then logically you should also use ss:mm:hh
No, because in most cases the most important information about a date is the day, then month, then year. It also matches the way we read dates. For the time it's typically the hour, then minutes, then seconds. YYYY/MM/DD is better when naming files, but in UIs I much prefer DD/MM/YYYY, it's just more natural to the way we read.
-
Heretic!
YYYY.MM.DD is the correct format.
small correction: YYYY-MM-DD to avoid common special meanings chars
-
This is stupid AF.
YYYY/MM/DD
This is the best choice.
/isn't a valid char in filenames, yyyy-mm-dd is better -
This post did not contain any content.
rfc3339 my beloved
-
Waiting for the ISO 8601 & 9001 gang to show up and promote YYYY-MM-DD.
Edit: That took seconds, a very punctual bunch.
-
For consistency, Americans should adopt mm:ss.hh MM-DD-YYYY.
For consistency, Europeans should adopt ss:mm:hh DD-MM-YYYY.
See how ridiculous that is? ISO8601 or GTFO
-
For consistency, Europeans should adopt ss:mm:hh DD-MM-YYYY.
See how ridiculous that is? ISO8601 or GTFO
At least ss:mm:hh and DD-MM-YYYY are internally consistent, even if they aren't consistent with each other.
MM-DD-YYYY isn't even internally consistent.
-
This post did not contain any content.
iso8601 aka 2025-06-12
-
If you use DD/MM/YYYY then logically you should also use ss:mm:hh
Or just use ISO8601 whi uses hh:mm:ss and well it is an ISO standard, but at least DD:MM:YYYY makes more sense than what Americans are doing.
Also 4th of july ....
-
Immediate red flag, we all know that YYYY/MM/DD is the only acceptable perfect date
Actually YYYY-MM-DD is better since it can be used basically everywhere and with / it can't be used in filenames
-
Let's not forget that technically you have to pay for ISO8601, despite it being nearly useless as a standard because it allows several incompatible formats to coexist.
Fucking wild.
Only if you want to say you have the certification for it, you can use it if you want, that is fine
-
After all the self-important blowhards in the committe were satisified that they had put their fingerprint on the ISO8601 document with bullshit like "year-month-week" format support and signed off, they went home.
The rest stayed behind, waited a few minutes to be safe, and then quickly made RFC3339 like a proper standard.
This is what RFC3339 vs ISO8601 feels like.
ISO8601 is YYYY-MM-DD nothing to do with weeks and isn;t the only difference of RFC3339 that you can use a space instead of a T in between the date and time?
Also RFC3339 is only an internet standard while ISO is a generally international standard?
