Also there is a heated debate that the UK is doing dates "the right way" and the US is wrong. Other than that people from Europe seem to think all of their practices are better than others, what is the possible reasoning that the order of numbers in a date string could have a right and wrong solution?
The argument is that ordering the numbers based on the size of units makes things easier and more useful. Both DD-MM-YYYY and YYYY-MM-DD follow this pattern, and both have their advantages/disadvantages. The latter is especially useful due to alphanumerical sorting.
How does it make it easier and more useful?
Lexical sort ordering without parsing the date string is a great property.
But clearly in human terms it’s never going to be a solved issue! Nobody is looking for a solution, and everyone likes their own convention. Mutual understanding is what’s important.
The fact we have divergent date string formats is most frustrating because for many dates (up to the 12 of every month) it is ambiguous which format is in play.
Why? Why is the date even a string in the first place? It ought to be internally represented as 3 numbers. Or a Unix timestamp. Convert it to months, days, and/or years as appropriate right before printing.
So these are good.
- year / month / day
- day / month / year
And this is bad.
- month / day / year
Personally, I write the month out if I'm not using 8601 formatting to avoid any ambiguity.
For any sort of recordkeeping, though, I think it's preferable to go full on YYYY-MM-DD. It's more thorough, precise, and sorts properly on a computer.
"May 3" / "May 3rd" or "3 May" ?
Mm/DD/yyyy is a crazy format.
If it weren't for the fact that my month number and day number were the same, I don't think I ever would have gotten it right growing up
yyyy-mm(mmm)-dd
2023-07(Jul)-12
...
Why?
- Goes from biggest to lowest value (year, then month, then day)
- To remove any ambiguation, also shows month in alpha format.
- Still sortable :-D This is the best part I think.
- Unambiguous.
- Actually sortable.
- A standard (ISO-8601).
- Still human-readable.
- Is not tied to English.
Edit: Good point, bashinator <3
The problem is that it is not unambiguous.
If you see 2023-03-02 in the wild there will be people who assume it is 3rd Feb.
Please correct me if I am wrong.
.com.example.sub/path/to/folder/and/file.html
Though of course I only use numbers in the name - no month name.
Where's the assumption? On the alpha portion? The date internally can be stored as it is, this is only the display and the alpha portion can be localized.
Anecdotally, I worked for a British company that used YY/MM/DD and it regularly caused reliability issues during operations. Of course, they responded with, "What's wrong with the date? It's correct." Yes - correct, but not accessible especially operationally so. If you want to take advantage of a global userbase or workforce be prepared to have the tax of these kinds of features being necessary.
Heck no. That means your date changes if the instant<->date mapping changes (for example, adding a leap second, or your country changes their time zones). If it's a plain date, store it as an ISO 8601 date (for example, "2023-12-30"), or equivalent plain date format (such as Postgres DATE).
The full year is required to make it clear that 23-12-10 isn’t the day before X-mas eve in 2010
This goes beyond date format for me. Issues like these show that the company is not committed to listening to feedback and addressing issues. It erodes my trust in them. Given that they hold my passwords, trust is paramount.
Same with their decision of not adding 1 password 8 into the Mac App Store. I won’t install outside the App Store, so I’m sticking with 7. The moment that goes, so do I.
Bitwarden is incredibly clunky IMO. Not worth it. Yes it is cheap, but you get what you pay for.
For a cross platform solution, I think KeePass-based pw managers are great. Create a database, set up sync however, and just us a KeePass-style app on each device. The beauty is that it's only the database that matters, so switching between apps is pretty painless, and they can't hold your data hostage.
It's almost certainly a very vocal minority (of which I am a member) that is still on version 7.
(Funny thing was that some of the podcasters I listen to chided people quite derisively for being upset with 1P8. Fast-forward a year, those same podcasters are talking about how 1Password has sadly gone downhill ...)
The dates format formats correctly, I have a password I added a few days ago, says "modified 7.7.2023 15.59.44" ... and 5.7.2023 for the one before that. It's a little weird with the . but it's fine.
No complaints, it works perfectly well, much better than Lastpass ever did.
01 JUN 2023
> I am having trouble with the date formats on macOS. My passport expiry is shown in MM/DD/YYYY, even though my date locale is clearly set to DD.MM.YYYY. In 1Password 7, as far as I can tell, it used to be DD/MM/YYYY.
> I have literally had a ton of trouble because of this because I entered my passport expiry date wrong on an airline form. As both numbers in the date can be flipped and will still show a valid date, this error isn't easy to catch, either. After looking this up, it has been first reported over 1.5 years ago! That is not an acceptable timeframe!
I've already had some wrestling with incorrect date formatting in 1Password, but I recently added my family's passports and almost made the exact same mistake.
You could somewhat justify future support back when 1P 7.x was in support, but now that it's completely EOL (mobile app is unlisted), there's absolutely no reason for this. It's literally one system API call. (Which they're already using in the "modified/created" fields on iOS!)
Glad to have this reach the frontpage as 1Pass support has been unhelpful with this for months, so I‘m hoping to get some attention to this issue via this route.
My previous comment has already been quoted here, so I won‘t reiterate, but this issue is generally easy-to-fix, yet can have a huge impact if not working.
Very annoyed with 1Password’s product direction and support on this. Their customer focus has been off for a while in my eyes, sadly.
I really need to back everything up offline more frequently.