We're talking about how it's displayed on the frontend, not how it's stored on the backend

One persons front end is another persons back end.

Especially if you're a proctologist.

We use YYYY-MM-DD HH:mm:as on the frontend because it sorts lexicographically, which is useful for interactive tables.

There’s no need to have the sort value and the display value to be the same to allow sorting.

You can use data attributes for that

I think irrational’s point is that it’s trivial for any viewer, no matter the locality, to identify the date if there is no longer any ambiguity between date and month.