YES! I wish more people knew about RFC 3339. While I'm all for ISO 1601, it's a bit too loose in its requirements at times, and people often end up surprised that it's just not the format they picked...
Huh, I've never noticed how much bloat was in ISO 8601. I think when most people refer to it, we're specifically referring to the date (optionally with time) format that is shared with RFC 3339, namely 2023-11-22T20:00:18-05:00 (etc). And perhaps some fuzziness for what separates date and time.
I have autohotkey configured to insert the current date in ISO 8601 format into my filenames on keyboard shortcut for just this reason. So organized. So pure.
DD/MM/YY and YY/MM/DD are the only acceptable ones IMO. Throwing a DD in between YY and MM is just weird since days move by faster so they should be at one of the ends and since YY moves the slowest it should be on the other end.
I think most Americans do. Or at least it was taught that way in school when I was growing up. Maybe it’s because of the way we speak dates, like “October 23rd” or “May 9th, 2005”.
Regardless, the only true way to write dates is YYYY-MM-DD.
If you use DD/MM/YYYY, dumb sorting algorithms will put all of the 1sts of every month together, all of the 2nds of every month together, etc. That doesn't seem very useful unless you're trying to identify monthly trends, which is fundamentally flawed as things like the number of days in the month or which day of the week a date falls on can significantly disrupt those trends.
With MM/DD/YY, the only issue is multiple years being grouped together. Which may be what you want, especially if the dates are indicating cumulative totals. Depending on the data structure, years are often sorted out separately anyways.
YYYY/MM/DD is definitely the best for sorting. However, the year is often the least important piece in data analysis. Because often the dataset is looking at either "this year" or "the last 12 months". So the user's eyes need to just ignore the first 5 characters, which is not very efficient.
If you're using a tool that knows days vs months vs years that can help, but you can run into compatibility issues when trying to move things around.
The ugly truth no one wants to admit on these conversations is that these formats are tools. Some are better suited to certain jobs than others.
Japan is YYYY-MM-DD, but when we talk about dates where a year is unneeded, we just cut it off which leaves it in the US standard format of MM-DD, much to the annoyance of non-US foreigners living here.
You only think it fits with how it's read in English because that's how you grew up saying it so it sounds natural to you.
Your experience is not universal, and is in fact, a minority.
It's how it is read in English (simplified) aka american english. Brittish english doesn't do this nonsense, the talk in the correct format (first of january etc.).
(I'm sorry if i made some mistakes, english is my second language)
I grew up with DD.MM.YYYY. But I think, MM/DD makes sense in everyday usage. You don’t often need to specify dates with year accuracy. “Jane’s prom is on 7th September” – it’s obvious which year is meant. Then it’s sensible to start with the larger unit, MM, instead of DD.
Even in writing you see that the year is always given like an afterthought: “7th September**,** 2023“.
I like that for files, but not for written documents. When I label things I try to use the most intuitive/least confusing way I can think of: DD mmm YYYY. This comment is posted on 23 NOV 2023, for example.
I do prefer the abbreviated month with the yyyy mmm dd format. It makes things relatively easy to sort but you also don't have to worry about confusing others if you are referring to the 10th month or day for example.
Liberia and Myanmar also use imperial units, but they're both starting to move towards metric in recent years so soon the US truly will be alone in that
You're not wrong. through much trial and error in the 1990s I learned this was the most efficient & accurate & chronologically searchable way to date things.
Because for 99.99% of all situations, you'd already know what year and month it is, so the most readily available piece of information should be the day.
I'm an ISO 8601 guy but the MM/DD does make sense in American. We'll say Oct 20th for a date and then straight translate that to numbers 10/20. It makes more sense than counting in French. Ex. 60, 70, 80, 90
Have another go at this train of thought, mate... You're basically saying "MM/DD" is better at sorting chronologically than "DD/MM", since the year part is taken out of the equation, which is already the established consensus, and not ironical whatsoever. And the ISO standard is already to use YYYY-MM-DD, so that's the winner IMO, hands down. Japan is simply following that but using a slash as the delimiter.
When you search or do any stable sort, I would think you want your primary attribute to be the one with most finite values? That way you are front loading the pruning of the search space.
Only within the same century, which is an issue for those of us born last millennium (or managing systems from that time), and could be a real problem in 50-ish years when we could get the first duplicates.
Better to stick with YYYY-MM-DD for alphabetical sorting
Japan isn't on its own wavelength, most of East Asian does this, probably because they all decided they wanted to be like China: which was a government which governed more.
https://youtu.be/Mh5LY4Mz15o?t=1m7s
Most of Japanese hates the arbitary currender year resetting at each new emperor enthronrment. The conversion is ass and no one knows when it changes (bound to emperor's health) . Worst is its official year that govmt body accepts.
You are likely to only refer more than current era. If you're writing govmet grant application, renewing licence or certificate, chances are you mention events hapenned in previous era. You look up table for when the previous era started and ended, which era said year falls into, then convert for each year, each era. Extra minutes wasted every time instead of simply writing in Gregorian year.
Nah. With binary, you can lose one hex digit AND the max year would be 2047 (11 bits year, 4 bits month, 5 bits day). What's not to like about hex anyway?
Yes, they have two date systems in common use. It's only the year that changes though. And there's no way to confuse the two, usually. If you write "2023" instead of "令5" it's pretty obvious. I suppose there is a potential for confusion if one just writes a two-digit year though.
Whenever their Emperor changes, the year starts with a new name(年号, which translates to name of year(s)). This time it's 令和(reiwa). Before that it was 平成(heisei). It is very commonly used.