Perfect date
-
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
-
They should also add a timezone since most of us don't live at UTC zero timezones -> 2012-12-28T18:12:33+09:00
Most people communicate mostly with people in the same timezone's, partially because most countries only have one timezone.
-
Anyone that gives me a document or receipt or invoice with a date formatted DD-MM-YYYY should have a tire iron swung at their thighs
Multiple swings if they can't decide on using DD-MM-YYYY or MM-DD-YYYY or DD-MM-YY or MM-DD-YY or YY-MM-DD or YY-DD-MM
I rather have somebody write their invoices at DD-MM-YYYY cause there is a bigger chance it will most likely not be an invoice from a North American company which notriously cannot make proper invoices and most software that actually scans and processes invoices is based on the European standaard DD-MM-YYYY or on ISO8601.
-
When i first read a date, i want to see the thing that changes 74 times in my entire life first too
HA! if you even get to be 74!
But in some jobs the year is more important (bookkeeping/accounting) and doing YYYY-MM-DD automatically sorts your dates
-
This post did not contain any content.
YYYY-MM-DD if you're doing backup naming, easier to find
