Implementing RFC 3339 shouldn't really be that hard...carrylex@lemmy.world to Programmer Humor@programming.dev – 677 points – 3 months agoTemplate Further reading: RFC 3339 / ISO 860183Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentWell if it's a 32bit timestamp you're screwed after 19 January 2038 (at 03:14:07 UTC)I don't think modern systems use 32bit stamps anymore, the ones that do are built to faili don't think json is guaranteed to parse 64 ints by spec tho, unless you store them as stringsMaybe they're planning on dying before then? In which case they're fine.
Well if it's a 32bit timestamp you're screwed after 19 January 2038 (at 03:14:07 UTC)I don't think modern systems use 32bit stamps anymore, the ones that do are built to faili don't think json is guaranteed to parse 64 ints by spec tho, unless you store them as stringsMaybe they're planning on dying before then? In which case they're fine.
I don't think modern systems use 32bit stamps anymore, the ones that do are built to faili don't think json is guaranteed to parse 64 ints by spec tho, unless you store them as strings
Well if it's a 32bit timestamp you're screwed after 19 January 2038 (at 03:14:07 UTC)
I don't think modern systems use 32bit stamps anymore, the ones that do are built to fail
i don't think json is guaranteed to parse 64 ints by spec tho, unless you store them as strings
Maybe they're planning on dying before then? In which case they're fine.