undefined | Better HN

0 pointsdustedcodes1y ago0 comments

I know ISO 8601, but that doesn't answer my question. Let me rephrase this, why was a format intuitive to a machine chosen instead of a format which feels more intuitive to a human?

I think YYYY/MM/DD - YYYY/MM/DD will mean the correct thing to many more people than YYYY-MM-DD / YYYY-MM-DD, which I suspect many will interpret as an OR and not a RANGE.

0 comments

zamadatix1y ago

EDTF has advantages in less ambiguity. At the same time, Markwhen does also support non-EDTF dates too. The docs do a good job of explaining both https://docs.markwhen.com/syntax/dates-and-ranges.html

Personally I think it goes a little over-flexible on support for non-strict formatted dates to the point it becomes difficult to figure out what a given date string is going to result in rather than feeling easier to use. That's probably part of the reason the primary example uses the clearer format.

keybored1y ago

> intuitive to machines

Because the “humans” messed up so bad that there weren’t many options left for a simple enough standard.

I would prefer ISO 8601 too over some slight variation which is allegedly more intuitive for homo sapiens sapiens. To keep it simple.

raziel2p1y ago

Any time I see slashes in dates I do actually have to double-check whether it's DD/MM or MM/DD.

j / k navigate · click thread line to collapse