"What. No it’s month first,” responded his girlfriend Christine. The couple subsequently got in a huge fight and broke up, meaning their relationship only lasted from 10/01/2023-05/03/2024, with neither knowing if that is 6 months or over a year.
What a good line 😂
The Beaverton is great.
, with neither knowing if that is 6 months or over a year.
I mean, that's the kind of ambiguity that makes exes hot, right?
...right?
I didn't know it was called ISO8601 but I started naturally using it at work. It removes confusion among international colleagues, makes it way easier to sort data, and is also good for version control of docs.
Me too. It looks quite normal now and, yes, is great for file organisation.
YYYY-MM-DD crew checking in
I.e. 2024-10-13
Wait, is that the thirteenth of October, or Smarch 10th?
Oh, lousy Smarch weather!
Yes
ISO8601 is great and all, but even without a common standard, I feel it should either be largest to smallest unit, or smallest to largest. YMD or DMY. Anything else is just asking for misunderstandings.
YMD is the way to go, because it auto-sorts on a computer.
Even when you tuck on the time, or would you prefer 59:46:13-14:10:2024 :-) ?
Are computers the most important thing?
Usually when I read a date I hardly care about year, because most events I read about are within a year
Leaving aside the problem that you are choosing a date system depending on who is using the dating system and for what purpose, under that condition the most logical would be MM/DD/YYYY, which is truly terrible, so I'm going to politely ignore your argument.
Leaving aside the problem that you are choosing a date system depending on who is using the dating system
I'm choosing one for humans, that'd seem to be the group that uses date systems most. Picking a new datesystem for each purpose would be insane, but also exactly what's happening in computer systems.
under that condition the most logical would be MM/DD/YYYY, which is truly terrible, so I'm going to politely ignore your argument.
I fail to see that conclusion? Why would that be the most logical?
I'm not disagreeing in general, but I need to point out that this is like saying you should write Arabic numerals in order of decreasing powers of 10 because it autosorts on a computer.
It's the reverse. Computers automatically sort Arabic numerals and dates written in decreasing powers because those are the correct formats.
Well that throws out DD-MM-YYYY because it's second smallest, smallest, fourth smallest, third smallest....
Heh... not what I meant, but technically correct
ISO-8601 is the only true time format. Big-endian all the way, baby!
I also only use data formats that can be alphabetized.
My favourite is when you’re reading documentation for an API or an SDK or whatever and the examples show things like “2024-05-05” as the date where they’re both the same number and you can’t discern it at all. Like, use Halloween or Christmas or something as the date so it’s always obvious, eh?
07/05/09
9th of July 2005?
Unironically a major consideration for me if I was scheduling a C-section.
The rest of the world's date system is most certainly not DD-MM-YYYY.
Care to elaborate? In my part of the world it absolutely is, with only some confusion sometimes caused by American dates
Large parts of asia (and prob some elsewhere) use YYYY/MM/DD
Community dedicated to the international standard YYYY-MM-DD date format.