Bob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 2 年前Everyday, as an Americanmidwest.socialexternal-linkmessage-square319linkfedilinkarrow-up11.31Karrow-down146
arrow-up11.27Karrow-down1external-linkEveryday, as an Americanmidwest.socialBob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 2 年前message-square319linkfedilink
minus-squaredan@upvote.aulinkfedilinkarrow-up3·2 年前Some ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up6·2 年前The ones without separators tend to be for server/client exchange though.
minus-squaredan@upvote.aulinkfedilinkarrow-up3·2 年前I agree but they’re hard to read at a glance when debugging and there’s lots of them :) Having said that, a lot of client-server communications use Unix timestamps though, which are even harder to read at a glance.
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up1·edit-22 年前At least it’s human readable and not protobuf 😬 * though the transport channel doesn’t really matter it could be formatted this way anyhow.
minus-squareShardikprime@lemmy.worldlinkfedilinkarrow-up2arrow-down1·2 年前I mean I like this one without the separations
ISO8601 gang
Represeeeeent!
Some ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
The ones without separators tend to be for server/client exchange though.
I agree but they’re hard to read at a glance when debugging and there’s lots of them :)
Having said that, a lot of client-server communications use Unix timestamps though, which are even harder to read at a glance.
At least it’s human readable and not protobuf 😬 * though the transport channel doesn’t really matter it could be formatted this way anyhow.
I mean I like this one without the separations