@carrylex@lemmy.world to Programmer Humor@programming.dev • 1 year agoImplementing RFC 3339 shouldn't really be that hard...lemmy.worldimagemessage-square79fedilinkarrow-up1696arrow-down10file-text
arrow-up1696arrow-down1imageImplementing RFC 3339 shouldn't really be that hard...lemmy.world@carrylex@lemmy.world to Programmer Humor@programming.dev • 1 year agomessage-square79fedilinkfile-text
minus-square@BatmanAoD@programming.devlinkfedilink5•1 year agoSorry, why would you be “boned” if you have UTC time? Are you thinking of the case where the desired behavior is to preserve the local time, rather than the absolute time?
minus-squareRoselinkfedilink3•1 year agoNot exactly boned but it probably doesn’t make practical difference to store “local time + tzinfo timezone” than just UTC time. You record an event occurring at local time You store it as UTC Local time zone definition changes Well whoop de loo, now you need to go through tzinfo to make sense of the past data anyway rather than relying on a known offset Even if you store everything in UTC, you may be safe… but figuring out the local time is still convoluted and involves a trip through tzinfo.
Sorry, why would you be “boned” if you have UTC time? Are you thinking of the case where the desired behavior is to preserve the local time, rather than the absolute time?
Not exactly boned but it probably doesn’t make practical difference to store “local time + tzinfo timezone” than just UTC time.
Even if you store everything in UTC, you may be safe… but figuring out the local time is still convoluted and involves a trip through tzinfo.