4 ms·
> Of course, mnemonics 1-2-3-4-5-6-7 (1st month, 2nd day, 3rd hour, 4th minute, 5th second, 6-th year, 7th timezone) is harder to remember than mmHHMMssSSYYyy c
by masklinn 4y ago
> Of course, mnemonics 1-2-3-4-5-6-7 (1st month, 2nd day, 3rd hour, 4th minute, 5th second, 6-th year, 7th timezone) is harder to remember than mmHHMMssSSYYyy crap that is different in different languages.
Very much so. The latter is at least portable between cultures, because a month is a month, unlike "1".
And then of course you've got all the collisions like weekday (which for some reason does not follow the US standard either) or yearday, the ambiguities (like sub-seconds which can be either 0 or 9), and the outright missing fields (week numbers? week-years? No comprendo, señor..)
- divan 4y agoVery much so? Let's put it to the pragmatic challenge. What will be the output of Go's "Jan 2006" and of R's "%B %h %M" format strings? Don't google.
- deleted 4y ago[deleted]
- masklinn 4y ago“Jan 2006” and short month, short month, minutes?
- divan 4y agoTo be clear "Jan 2006" - is a format string. Current date would yield "Dec 2022", obviously. R example - it's "Long month, hour, decimal minute", so something like "December 15 35" So you got Go format style right, and alphabet-style wrong. But Go's format is worse, right?