News for hackers. Stuff that matters.
Re:Slack’s Incident on 2-22-22 by true_religion on Tuesday April 26, 2022 @08:38PM (#31174920)
I instinctively felt that the ambiguity ought to not truly exist, but I wanted to find some backing. According to this: https://en.wikipedia.org/wiki/Date_format_by_country

… all the major predominantly English speaking counties will use mostly hyphens in the dd-mm-yyyy format. So although there is ambiguity, it’s easily resolved by picking that as the default mentally and only back tracking on failure.

Now in the more general case, this whole thing feels like a lieutenant/leftenant situation. We are annoyed simply because it’s not they way that we do things in a peculiar case, when otherwise the language is fully intelligible.

Re:Slack’s Incident on 2-22-22 by dllthomas on Wednesday April 27, 2022 @02:12PM (#31183654)
> … all the major predominantly English speaking counties will use mostly hyphens in the dd-mm-yyyy format.

Yes, which makes reasonable the complaint about mm-dd-yyy.

> So although there is ambiguity, it’s easily resolved by picking that as the default mentally and only back tracking on failure.

This is both more work and also error prone in the general case (although it works out fine in this case).

> Now in the more general case, this whole thing feels like a lieutenant/leftenant situation.

Not at all. Whether I read "lieutenant" or "leftenant", I know what you're talking about. If I read 2-10-23, I might miss your birthday party.

Re:Slack’s Incident on 2-22-22 by tjoff on Wednesday April 27, 2022 @01:43AM (#31176732)
Even people in non-English-speaking countries write in English all the time, especially on the Internet.

Picking one default and back-tracking on failure really isn't that comforting nor the constant reminder that the date you thought it was might be something else.