Friendly to who?

Holy cats, that sounds like a nightmare.

Hey, that sounds like my cloud storage providers auto billing system.

“Your auto renewal will draft on 08/09/23.”

Is that August 9th or September 8th? Literally depends on where the person you ask is in the world.

I must be missing something.

They’re trying to make it look fake!

Why are you splitting and delimiting a date object? Convert it to a shallower object if that’s what you need

Honestly, even a lowercase t.

Using T as a delimiter is mental

You get used to it.

You should be localizing it before displaying to users. Let their browser/platform decide.

Personally I can’t stand the format you’ve shown. I also can’t stand periods being used for phone numbers, e.g. 555.555.5555.

Although I actually like that format a lot, we use characters to help elicit context. 2023/08/09 is fine since we have been using / for dates for so long. Also it blows my mind why people don’t use : in 24 hour times. 16:40 is great, no am pm bullshit and you immediately know I’m talking time.

Same number of pixels, they are just different colours. But you still paid for them.

Linux has been able to handle that since the 90s.

Tough luck if you are using NTFS file system. All my homies use EXT4.

That’s not ISO8601

In a programmatic context? Sure.

In an “I want to be able to comprehend this by glancing at it” context: absolutely not.

2023-08-10 15:45:33-04:00 is WAY more human legible than 1691696733.

Whenever I’m passing a date from a website backend to frontend I’ll usually send it inside something like <span> then have JavaScript convert it to a string based on the browser’s localization settings.

So many websites I see for error reporting, etc always throw everything out as UTC and it drives me crazy. It would be nice to just have an HTML tag for ISO-8601 (or even UNIX as done here).</span>

I’m pretty sure it’s because of the way we say it. Like, “May 6th, 2023”. So we write it 5/6/2023.

That said, I think it’s fucking stupid.

America believes month/day/year for some stupid fucking reason.

It’s because of Great Britain. We adopted it from them while a bunch of colonies and it regionally spread to others.

America didn’t change, probably because we have been so geographically isolated (relatively speaking), whereas the modern day UK did change to be more like Europe.

People get so goddamn hot and bothered by things that ultimately don’t matter almost like it is a culture war issue. Americans maintain the mm/dd/yyyy format because that’s how speak the dates.

I wouldn’t say it is us Americans who “find it hard to read” if someone from elsewhere in the world sees an American date, knows we date things in the old way they used to date things, and then loses their minds over having to swap day for month. Everyone just wants to be contrarian and circle jerk about ISO and such.

Us devs, on the other hand, absolutely should use the same format of yyyy-mm-dd plus time and time zone offset, as needed. There’s no reason, in this age, for dates to be culturally distinct in the tech space. Follow a machine-first standard and then convert just like we do with all other localizatons.

But hey, if people want to be pedantic, let’s talk about archaic gendered languages which are completely useless and has almost zero consistency.

Day/month/year is not in the same category as y/m/d. That crap is so ambiguous. Is today August 9th? Or September 8th? Y/m/d to the rescue.

Because who cares what day it is without knowing the month first.

I am an American and I use it religiously for the record. Especially for version numbers. Major.minor.year.month.day.hour.minute-commit. It sorts easy, is specific, intuitive, and makes it clear which version you’re using/working on.

The letters make no sense to me. Like Jul, Jun, I’m constantly mixing them up. Give me a good solid number like 07 or 10. No mixing that up. Higher numbers come after lower numbers, simple as.

Epoch is also acceptable if humans don’t need to understand it

If you’re on Linux exiftool can get the creation date for you: exiftool -p '$CreateDate' -d '%Y-%m-%d' FILENAME, and you could run tgat in a loop over your files, something like:

mkdir -p out
for f in *.jpg
do
createdate=$(exiftool -p '$CreateDate' -d '%Y-%m-%d' "${f}")
cp -p "${f}" "out/${createdate} - ${f}"
done

Obviously don’t justbgo running code some stranger just posted on the internet, especially as I haven’t tested it, but that should copy images from the current directory to a subdirectory called ‘out’ with the correct filenames.

I did this in the past and I would search through my notes… If I had notes ffs.

Where is here that November = 9? Probably somewhere you’ve had a long day

We basically never say the sixth of November. It sounds positively ancient.

When is your independence day, again?

Anyway, in Australia (and, I suspect, other places that use DD/MM/YYYY) we use “{ordinal} of {month}” (11th of August), “{ordinal} {month}” (11th August), and “{month} {ordinal}” (August 11th) pretty much interchangeably. In writing but not in speaking, we also sometimes use “{number} {month}” (11 August). That doesn’t have any bearing on how we write it short form though, because those are different things. It’s not the defence many Americans seem to think it is of their insane method of writing the short form.

Saying it like that is no problem and not ambiguous. Writing it like that makes no sense though.

I’m canadian and I’ve always prefered this format for the same reason. 11/6/23 is november 6th 2023, not the 11th of June 2023, that’s weird.

It is a bit of a chicken and egg question though. Because do Americans not say it that way because of the date format or is that the date format because you don’t say it that way?

Because in countries using DD.MM.YY we absolutely do say 6th of November.

Three ways that people actually use. YYYY-MM-DD, DD-MM-YYYY, and MM-DD-YYYY (ew).

AFAIK no-one does YYYY-DD-MM, DD-YYYY-MM, or MM-YYYY-DD… yet. Don’t let the Americans know about these formats, they might just start using them out of spite.

Twelve ways if you count two-digit years. My nephew was born on 12/12/12 which was convenient.

In Danish, it’s said like 1st of June.

Flemish here (aka dutch-speaking). We say first June, sixth November etc. English isn’t our native language, so M/D/Y is weird as fuck and completely illogical to us.

Yes it is objectively weird.

When you write down “07/01/1967” are you unaware that it is unclear whether you’re referring to July 1st or January 7th?

And despite the fact that you’re writing something down for the express purpose of communicating information, and you’re choosing to shorten it’s written format to save time and space, you’re ok with either

a) just leaving it ambiguous and communicating poorly

or

b) having to write extra words to give it context, taking up more space than just writing out “July 1st, 1967”?

1967/06/01 clearly communicates we’re starting with the year and going biggest to smallest time increments. There is no ambiguity as to which order it’s ever in, and it’s far shorter than the full written date.

At a fundamental user experience level, it is objectively nonsensical to choose the American date format when your goals are 1) clearly communicating a date and 2) doing it shorter than writing out the words.

The 3 "M"s are not numerical, but indicate characters. For example 01 Jan 2023.

If you’re writing on paper, 10 August 2023 is superior.