3 ms·
If you are going to design something using a time code the most obvious solution is probably to choose your own zone. When you realize that doesn't apply to any
by rocqua 9y ago
If you are going to design something using a time code the most obvious solution is probably to choose your own zone.
When you realize that doesn't apply to anyone else, UTC is the next option. Especially because it means you don't need to deal with user configuration.
As for ISO8601, that probably results from people looking for some standard to help with compatibility.
If you just mean YYYY-DD-MM HH:MM that is just nicely ordered. Actual ISO8601 would yield something like: 2018-03-11T22:53:40+00:00
I personally really hate that T in ISO8601, but it is actually a standard aimed at being both human and machine readable.
All that aside, I think we can all agree that MM-DD-YYYY is just incongruous and stupid.
- philliphaydon 9y agoIt’s yyyy-mm-dd not yyyy-dd-mm....
- rocqua 9y agoYou are totally right, I got that wrong :( sadly it's to late to either edit or delete my shame.
- ygra 9y agoWell, the T can be omitted if reading and writing parties agree: »NOTE: By mutual agreement of the partners in information interchange, the character [T] may be omitted in applications where there is no risk of confusing a date and time of day representation with others defined in this International Standard.« And I think SpaceX wouldn't even have the obvious option of using their own time zone. AFAIK mission control and launch are in different time zones anyway, so UTC is really the only sane option to make sure everyone refers to the same time.