Bob to Lemmy Shitpost@lemmy.worldEnglish · 22 days agoEveryday, as an Americanimagemessage-square320fedilinkarrow-up11.29Karrow-down143
arrow-up11.25Karrow-down1imageEveryday, as an AmericanBob to Lemmy Shitpost@lemmy.worldEnglish · 22 days agomessage-square320fedilink
minus-squaredan@upvote.aulinkfedilinkarrow-up3·22 days agoSome ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up5·21 days agoThe ones without separators tend to be for server/client exchange though.
minus-squaredan@upvote.aulinkfedilinkarrow-up2·21 days agoI 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-220 days agoAt 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-up2·21 days agoI mean I like this one without the separations
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