Leaving aside the problem that you are choosing a date system depending on who is using the dating system and for what purpose, under that condition the most logical would be MM/DD/YYYY, which is truly terrible, so I'm going to politely ignore your argument.
- Posts
- 8
- Comments
- 12
- Joined
- 3 yr. ago
- Posts
- 8
- Comments
- 12
- Joined
- 3 yr. ago
Bitcoin @discuss.tchncs.de Crypto Has Bought The 2024 Election!
Bitcoin @discuss.tchncs.de Kingdom of Bhutan holds over 13,000 Bitcoins
Bitcoin @discuss.tchncs.de Incredibly bullish top comment on /r/Buttcoin thread... But they still think it's a scam
Bitcoin @lemmy.ml Would be nice to get everyone into the same Bitcoin community
Bitcoin @discuss.tchncs.de Summary of the latest IMF paper on Bitcoin
Bitcoin @discuss.tchncs.de Interesting story about gold smugglers - should have bought bitcoin
196 @lemmy.blahaj.zone Life rule
Bitcoin @lemmy.ml Where does electrum store the private key when unencrypted?
So the first point was that depending on your files/archives and how you access it, year or month or day may be more relevant to the user, which is why I was saying it's dependent on the user, so I don't agree that a human centric solution is always going to say the year is less relevant.
And then if we are going to prioritize organizing the numbers in such a way as to save the eyes a millisecond of time, for standard usage month would be the orienting date since you need to make sure you are looking at today's month, and then day would be the next necessary date, and then you'd still need the year there, so you'd end up with Month Day Year. Putting Day first would be just as wrong as putting year first because it is irrelevant until you establish the month, it's too granular.