6 ms·
ISO 8601 is the only way to go. With that said, it's hard to control what systems others use. I frequently work with datasets that have 4-5 different timestamp
by TrackerFF 3y ago
ISO 8601 is the only way to go.
With that said, it's hard to control what systems others use. I frequently work with datasets that have 4-5 different timestamp formats.
One of the most annoying bugs I've worked on, was in a table where almost everything followed a DDMMYYYY format - sans a 2-3 month period where the dates were flipped to MMDDYYYY
- Thorrez 3y agoDoes ISO 8601 fix any of the problems mentioned in the article? It doesn't really seem relevant to me.
- sitkack 3y ago> doesn't really seem relevant to me Isn't this overly 'you' centric? Wouldn't this require access to your inner monologue? Doesn't seem like a referentially invariant supporting argument, to _me_.
- falserum 3y agoCharitable interpretation of previous comment would be “I think it does not seem relevant to problems specified in the article”. Iso 8601 is about date formatting, while article is about a bit orthogonal to that. (But I agree/hope that ISO 8601 is the future that is less ambiguous than current state)
- sitkack 3y ago> I think it does not seem relevant to problems specified in the article Is a low effort way to make someone form a rebuttal in response to no argument. It is pseudo intellectual way to sound smart while offering nothing in return. As if that persons opinion has weight because “they don’t see the relevance”, I know lots of people that “don’t see relevance”. Is our responsibility to educate their feigned confusion?
- Thorrez 3y agoI was saying that TrackerFF's post seemed to me to be unrelated to the article, so I was confused why it was posted. I'm sure other HN readers were confused by the comment as well. I was asking for clarification. TrackerFF or someone else could then clarify the relevance, which I and other HN readers would find useful. My confusion wasn't feigned. I'm actually confused how the comment was relevant to the article. Someone being confused and asking for clarification is a common way that conversations progress and learning happens. It's no one's responsibility to comment on HN. If someone wants to discuss this, that person can reply.
- falserum 3y agoMist likely it was: It’s a low effort proxy for “this comment is most probably written only after only reading the title”
- Thorrez 3y agoSorry, I phrased it confusingly. I should have just said "it doesn't seem relevant".
- LikesPwsh 3y agoThat bug is probably because of someone opening a CSV in Excel. It's a common one, sadly. Anyone using the US date format for transfer or storage (debatably also display) should consider it a bug.
- praash 3y agoAfter all these years I still feel Excel cannot handle a fully compliant datetime string.
- teddyh 3y agoI actually prefer RFC 3339 over an not-freely-available ISO standard.
- praash 3y agoISO 8601, ironically, also defined acceptable a (now deprecated) set of truncated date formats such as YY-MM-DD and YYMMDD.
- pepoluan 3y agoAs long as it is now deprecated then it's no longer ironic.
- rini17 3y agoOkay but it does not standardize location. To reliably manage local time conversions, including location together with date/time is the only way.