Re:Go Date Format
by ustolemyname on Sunday January 25, 2015 @07:13PM
(#8944837)
ISO ordering would make expressing time in AM/PM ambiguous, i.e. the format string "2:05PM".
[ Parent
| on HN ]
Re:Go Date Format
by tjradcliffe on Sunday January 25, 2015 @09:56PM
(#8945343)
But why would you want to? FSM intended us to use ISO-8601 dates and nothing else. If you disagree, I'll meet you on 18/06/12 at 2:04 to discuss the issue, although you have no way of knowing what date or time that string actually refers to.
We have a perfectly good, unambigious date and time format. It's true that many users are deeply committed to ambiguous formats, but we should at the very least be trying to dissuade them from using them by making ISO formats the default.
Re:Go Date Format
by BenDaglish on Monday January 26, 2015 @04:08AM
(#8946106)
I messed up - I meant 2001-02-03 04:05:06 , in which case 2:05PM would be format "4:05PM", (or 16:05) . All that'd happen would be the year and seconds swap order in the "123456" format - but as I said, it's a minor quibble.
Re:Go Date Format
by lifthrasiir on Sunday January 25, 2015 @07:35PM
(#8944918)
12:34:56 2007-08-09 would work equally, though. (EDIT: oops, no.)
Re:Go Date Format
by ustolemyname on Sunday January 25, 2015 @08:20PM
(#8945073)
How do I cleanly express single digit minutes?
The format string "4 minutes after 12", is unique, but it's not clear that I could turn "34" into "4". Similar for the hour (12 is now 2).
That would also break the "Print this exact time in the format you're currently using" method of creating a compatible time format string.