No, in Russia, it was still October. They were a bit behind the rest of the world. However, yes, in the yes of the world it took place in early November.
When people are talking out loud, does anybody actually say “23 August”?
“August 23rd” is so much more natural. Because (A) it rolls off the tongue easier, and (B) it’s more logical. Since people seldom talk about a multi-year timeframe in most instances, it’s more natural to identify the big unit of time (the month) first, and then introduce more specificity by sub-dividing that unit into smaller units (days). This has the added advantage of being EXACTLY how we talk about time of day. The hour (big unit) comes first, and then the minute (smaller sub-division of time). Nobody writes the time “45:9 AM.”
Anyone in the US military does, and every time they speak a date. People who are in military-adjacent industries probably do to. My former employer used that format and it was commonly pronounced just as written.
You have inadvertantly hit upon the nub of this whole date format thing. Humans are lazy and prefer to say or write the least possible, with the rest inferred by the audience from context. And with a fuzzy notion of precision. Computers prefer zero inferring and everything (including precision) explicit. The ideal format for short + variable precision + inference of the rest is very different from the ideal format for universality and explicit precision.
Lastly, computers prefer one format everywhere for everything whereas humans prefer different formats for different degrees of specificity and different operating contexts. “Next Tuesday” is great when you know from context when that was said. When someone reads this post a month (or 3 years) from now, the same words “next Tuesday” will refer to a very different point in time. OTOH “2023-10-03” will be static, referring to “next Tuesday” as I write but not “next Tuesday” a month from now.
Why is it “more sensible”?
I am with
Just because other nations do it differently, doesn’t mean the USA is wrong.
And this map shows not all of the rest of the world uses DD-MM-YY: Quite a bit of asia uses YDM instead.
In fact, international experts are pushing for the iso YYYY-MM-DD.
On the linked map, Canada is in the grey zone (anything goes)…
But there is an important point here: local numerical formats follow local text/spoken conventions. This is about standardizing a numerical format only. The local text/spoken conventions will continue.
DMY is small to large
YMD is large to small
MDY is neither.
It’s like writing your address
Spring Street House # 44
MA, Springdale, USA
That breaks down as soon as you have multiple languages. For instance, for dates in August, the Canadian passport has a workaround that shows DD AUG / AOÛT YYYY.
This explains why people refer to individual months as “August of 2023” instead of “2023 August”. No, wait, it doesn’t. The logic you’re finding just isn’t there.
All forms of communication break down once you have multiple languages. That can’t be helped.
In Europe, addresses are often written pretty close to this. I’ve seen Finnish addresses that go something like this:
Esplanadi 23 C 14
FI-2300 Helsinki
Where Esplanadi is the street name, 23 is the street address of the apartment building, C is the entrance of the building, and 14 is the apartment number, accessible only by that entrance (it was a large building–and imagine trying to find the apartment if you don’t know this), FI is the country code, 2300 is the postal code, and Helsinki is the city.
Note that there is no province name. This causes issues when I order books from a place in Belgium. Their order form has literally no place to put in a province name, and it formats shipping addresses for print in the this way, which makes Canadian or US addresses look really, really weird. If it wasn’t for the postal code, my package might not make it to the right Springfield.
I know. And that’s a less logical way to write an address than big to small (China) or small to big (many places including the USA, almost).
Just because the Americans or Finns do it a particular way, doesn’t make it logical/sensible/intuitive nor does it make it wrong.
It’s not more natural. It’s more familiar to you because you’re an American. So it rolls off your tongue because your tongue is accustomed to saying “Aug 23” rather than “23 Aug”. It is nothing more than habit.
As to “logical” you’d have to define what sort of logic you mean.
This is similar to nouns and adjectives in English. The standard grammar is that the various flavors of adjectives all come first in an arbitrary but recognizable order by category, then finally the noun they modify. Which is ignorant and backwards. Contrast:
- The big red rubber ball (standard English)
- The red rubber big ball (an example with the adjective categories out of usual order)
- The rubber red big ball (a different example with the adjective categories out of usual order)
- The ball big red rubber (An example of US military-style logistic nomenclature that is far more logical, but sounds really foreign and “unnatural” until you’re used to it. Then you wonder why ordinary English does it so stupidly backwards.)
I’ve noticed a lot of non-Americans write American addresses as
John Smith
10 Main Street
Springfield
ST 00000
because they think the comma in
Springfield, ST 00000
stands for a line break.
Although interestingly enough, the USPS standard for addresses dropped the comma between city and state a couple of decades ago. Using the comma is non-standard now.
Individual people addressing stuff whether by hand or by keyboard still tend to use it and it still works. But nobody preparing volume mail for USPS delivery will use the comma.
My granddaughter visited us a couple weeks ago and, while here, decided to apply for a Canadian passport. She has already received it (in Chicago).
Quebec has used the YYYYMMDD standard for a couple decades. I’m not sure about the rest of Canada (too lazy to look up my passport). It sure makes sense and is easy to sort. A friend retired on the second day of second month of the second year of the millennium so there could be no confusion.
Wait, I thought that Springfield was in North Tacoma.
Springfield is in one of the states that meet at the 5 Corners.
Why is this a one way street? Regardless of which way is ‘better’ couldn’t this be a European business losing money in the USA for not using the ‘Amenican’ format just as easily?
It’s not entirely one-way, but in my experience it’s more than 95% one way.
My experience = working for either US companies with significant operations outside the US, or working for European companies with much or most of their business in the US. For 30+ years.
The Europeans in particular are very cognizant of differences in culture, language and customs. On the other hand they sometimes think what works in Texas will work in New York or vice-versa and come a-cropper that way. Also are sometimes shocked by the size of the country (combined with very poor train service). But they seem to adapt pretty quickly.
I’ve known Americans the have complained about the parking in major European cities for 8-10 years, because they are trying to drive everywhere.
I think the T is an excellent choice! Punctuation is optional everywhere in the code (except as a decimal mark if fractional seconds are included). This is valuable, for example, when naming files or variables or functions or other digital constructs (as various digital systems prohibit various punctuation marks). A letter character is allowed in many more constructs than any particular punctuation is. It’s quick ‘n’ easy to look for the T programmatically, and “T” is never used as a delimiter in any other programming stuff IIRC. For many uses of 8601, the “T” is the only delimiter.
