Perfect date
-
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? -
For consistency, Europeans should adopt ss:mm:hh DD-MM-YYYY.
See how ridiculous that is? ISO8601 or GTFO
The european one is sorted based on importance to see. The day is more important than the month which is more important than the year. The hour is more important than the minute which is more important than the second
-
This fucknuts who thinks day should come before year, hah!
Give me YYYY-MM-DD, because dashes are better than slashes any day of the week.When i first read a date, i want to see the thing that changes 74 times in my entire life first too
-
Happily!
So, first epoch time. It's a pretty robust standard, covers many use cases, has few edge cases... but it's specifically for machine usage, since it's not human readable and it's not reversible into the past (pre-1970).
ISO 8601 (depending on the annum), by the text of the documentation, these are all valid dates:
- 2007-04-05T14:30
- 2007-04-05T12:30−02:00
- 2007-04-05T14:30Z
- 200704051430
- 07-04-05T14:30
- 2007-95T14:30
Etc.
RFC 3339 (& RFC 9557, it's newest modification) is actually a subset of ISO 8601 and is far more prescriptive. For example you must have a timezone designator. You must have a separator between the date and time. You must use a dash between date elements and a colon between time elements. You can easily add standardized subseconds.
- 2007-04-05T12:30−02:00
- 2007-04-05 14:30Z
This means that RFC 3339 is much easier to parse and use by both machines and humans.
This page (reddit, I know...) has a great summary, and so in the interest of knowledge and attribution I'll link it: https://www.reddit.com/r/ISO8601/comments/p572xy/rfc_3339_versus_iso_8601/
This website allows you to more directly compare the two interactively.
https://ijmacd.github.io/rfc3339-iso8601/ISO is a wider standard than the RFC standards though which is only for the internet
-
For consistency, Americans should adopt mm:ss.hh MM-DD-YYYY.
You monster
