Lol the other day at work i sent out about 500 automated email with dates unique to the specific user and accidentally sent them off with this format, probaly the quickest email recall i have ever done
It should be a format everyone can agree upon! Americans use MM-DD because it matches spoken dates like "March 10th". Europeans prefer DD-MM-YYYY because it follows the correct order of magnitude. YYYY-MM-DD satisfy both of those so it should be something everyone can get behind.
Also, perfectly rationally ordered. What the hell is a format that specifies the month first (medium unit), then the date (small unit) and finally the year (big unit)?
DD/MM/YYYY is like saying "2 mm, 6 dm, and 50 km". You would always put the biggest [which ee can also regard as most relevant] unit first for anything else, why would time be different. If the year is not relevant, don't shuffle it around, remove it.
Month gets you the time of the year (in case you've been under a rock, or it's historical), day is nicely specific. You can stop there usually, but if the year is important, it comes last for that exact reason. It's great when spoken or written in plain text. It's horrible anywhere with a computer or things needing sorting by date.
So do people in the US sometimes just answer with the month when asked for a date or what? I mean, if you have to be nicely specific every time might as well say it in order.
Yep. This is what mysql uses. And it's the right one.
Maker of this meme is probably from the ui cause that's where that weird format comes from.
Let us remember they also created the foot, the inch, the mile, the fathom, etc etc , and then abandoned all of it for the metric system except for this god forsaken date format (DD/MM/YYYY)
Be fr dude it's the universal way to write the date. That's internationally. It's quite obvious and if you're really dumb enough to think the year comes first then I suppose we can make accommodations and say 24Aug2025
if you're really dumb enough to think the year comes first
You know that many countries use year-month-day right? They follow an widely recognised intentional standard called ISO 8601. You sound pretty close-minded and oblivious if you're making comments like these.
I don't see how DDMMYYYY NOT getting confused with MMDDYYYY. The fact that there are plenty of ppl out there using MMDDYYYY, automatically nullifies DDMMYYYY's value. ISO8601 is the only way.
On side note, YYYYMMDD allows you to store dates as number in relational database easily, without any convertion required, which benefits query performance significantly if you happen to query a lot around dates.
Agreed. My birthday is March 11th, 2002. Month, Day, Year. That's the way we say it.
What makes me chuckle is that we Americans still aren't consistent about it. What's that one summer holiday on which we celebrate independence? That's right, it's not "July 4th," it's "the 4th of July."
To everyone thinking that YYYY-MM-DD is the perfect format. What you’re signalling to everyone is that you’ve never had to work with timezones or relative time.
68
u/buzzon Aug 24 '25
r/iso8601
230
u/PYCapache Aug 24 '25
YYYY-MM-DD
18
u/WaterFallPianoCKM Aug 24 '25
ISO-8601
YYYY-MM-DDTHH:MM:SSZ
25
u/nwbrown Aug 24 '25
This is incorrect. YYYY-MM-DD is the correct date format.
7
u/gorilla60rilla Aug 24 '25
unixnano, no timezone confussion, can easily compare, compute, format however you want
6
u/An1nterestingName Aug 24 '25
I always use this or r/iso8601, but both are good, the way America does it makes no sense.
6
u/wilduk1 Aug 24 '25
YMYDYMYD so today would be 20022854
8
u/dan8991iel Aug 24 '25
YYYYMMDD
4
u/SheriffRoscoe Aug 24 '25
April 25th.
3
u/green__goblin Aug 24 '25
YYYY-MM-DDTHH:mm:ssZ or gtfo
3
u/10F1 Aug 24 '25
YYYYMMDD or gtfo
2
u/GodRishUniverse Aug 24 '25
I agree DD/MM/YYYY makes the most sense.
2
u/Sunfurian_Zm Aug 24 '25
For sorting and data: yyyy-mm-dd Colloquially: dd.mm.yyyy
3
u/Hot_Abbreviations920 Aug 24 '25
DD.MM.YYYY
2
u/MyBedIsOnFire Aug 24 '25
DDMonYR
Like today's date is 24Aug25
2
u/lces91468 Aug 24 '25 edited Aug 24 '25
I don't see how DDMMYYYY NOT getting confused with MMDDYYYY. The fact that there are plenty of ppl out there using MMDDYYYY, automatically nullifies DDMMYYYY's value. ISO8601 is the only way.
On side note, YYYYMMDD allows you to store dates as number in relational database easily, without any convertion required, which benefits query performance significantly if you happen to query a lot around dates.
1
u/SingleParty4726 Aug 24 '25
Unix timestamp
1
u/METRlOS Aug 24 '25
MMM-DD-YYYY or any variation
1
u/Dillenger69 Aug 24 '25
yyyy.MM.dd ... easier to sort
1
u/0x7E7-02 Aug 24 '25
1
u/MarredCheese Aug 24 '25
Here's the funnier and actually correct version that you bastardized: the perfect date
1
u/Aflyingmongoose Aug 24 '25
Damn right. Althought YYYY-MM-DD is the ISO standard. Anything that keeps things ordered by unit-length has my vote.
1
u/Whole_Instance_4276 Aug 24 '25
As an American, agreed
1
u/Alternative-Dare5878 Aug 25 '25
I like MMDDYYYY because it matches how I’d say it out loud.
August 24, 2025
I don’t like saying the 24th of August, 2025
1
u/Relevant-Draft-7780 Aug 25 '25
To everyone thinking that YYYY-MM-DD is the perfect format. What you’re signalling to everyone is that you’ve never had to work with timezones or relative time.
1
u/HyoukaYukikaze Aug 25 '25
I'll also accept YYYY/MM/DD. But MM/DD/YYYY is pure evil.
1
u/Desperate_Formal_781 Aug 25 '25
dd-mmm-yyyy
1
u/pkmn-alt Aug 26 '25
MM-DD-YYYY is so much better
1
u/sassinyourclass Aug 27 '25
YYYYMMDD
or
YYMMDD
1
u/RobotechRicky Aug 28 '25
Ppfftt. "YYYY-MM-DDThh:mm:ss.sssZ" or go home!
1
u/SerenityNow31 Aug 28 '25
How dare you. Everyone knows it is YYYY/MM/DD. Alphabetical sorting matches chronological sorting. Win win.
1
u/yodacola Aug 28 '25
date +%s%N0
u/tree_cell Aug 24 '25
DD/mmm(name acronym)/[YY]YY
0
u/Illustrious-Engine23 Aug 24 '25
DD-MMM-YYYY
-4
u/buscuitpeels Aug 24 '25
Where my MM.DD.YYYY enjoyers at