Ok, but year-month-day (ISO 8601 or RFC 3339) is the only correct way to write dates. The two date formats in this image both suck (and even more so because people often can’t tell which one you’re using).
Eg, 2023-06-30, or with a time and timezone, 2023-06-30T09:54:45-0400.
that’s REALLY useful with official/computer stuff, but for everyday it’s pretty annoying to have to read “the deadline is twenty twenty three, July, 6th” when you already know it’s in July and in 2023. Often the only information you are looking for (the day) gets pushed in the end
It does, but in almost all cases where you are writing the date vs just saying it, the month is generally important since it’s often not certain when it will be ready, so written out M/D is generally more useful.
Ok, but year-month-day (ISO 8601 or RFC 3339) is the only correct way to write dates. The two date formats in this image both suck (and even more so because people often can’t tell which one you’re using).
Eg, 2023-06-30, or with a time and timezone, 2023-06-30T09:54:45-0400.
And it makes it’s alphabetical sort the chronological sort when naming files leading with the date
that’s REALLY useful with official/computer stuff, but for everyday it’s pretty annoying to have to read “the deadline is twenty twenty three, July, 6th” when you already know it’s in July and in 2023. Often the only information you are looking for (the day) gets pushed in the end
It does, but in almost all cases where you are writing the date vs just saying it, the month is generally important since it’s often not certain when it will be ready, so written out M/D is generally more useful.