Regardless of whether you think big endian or little endian is better, I think fans of both would agree that middle endian makes absolutely no sense.
Absolutely. The US date format makes no sense, and why not just do it like the entire rest of the world does? But no, America is just too special…
If writing the month as a number instead of in words, I almost always write dates in the little endian (yyyy-mm-dd) format because most people can easily figure out what I'm saying (the 4 digits in "yyyy" make it obvious that it's the year). I do not use the big endian (dd-mm-yyyy) format because if dd <= 12 and mm <= 12, people can confuse it with the middle endian format. I don't want someone confusing December 4, 2022 (04-12-2022) with April 12, 2022 (12-04-2022), for example. But when you write 2022-12-04, everyone knows what this means and nobody will confuse it with April 12, 2022 because yyyy-dd-mm is not a valid format anywhere.
For year agnostic events, relegating it to the end speeds things up.
It's worse than that. It's:
I don't encounter that one as much, so it tends to throw me occasionally... primarily because there is no "unit" included like there is in "3m" vs "3ft", so the field order is not always immediately obvious to me when the "day" field digits are =< 12.
And that makes sorting by file creation/modification time easy. Chop off everything before the "_" and then sort the remaining in alphanumeric order from left to right. Or convert to an unsigned integer and then sort the unsigned integers.
I would love that. I was never in the military but the 24 hour clock just makes sense to me.
Until we go to Mars. Then we'll need a 24-hour 40-minute clock.
