@Bob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish • 1 year agoEveryday, as an Americanmidwest.socialimagemessage-square296fedilinkarrow-up11.27Karrow-down145
arrow-up11.23Karrow-down1imageEveryday, as an Americanmidwest.social@Bob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish • 1 year agomessage-square296fedilink
minus-square@dan@upvote.aulinkfedilink0•1 year agoSome ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
minus-square@zqwzzle@lemmy.calinkfedilinkEnglish0•1 year agoThe ones without separators tend to be for server/client exchange though.
minus-square@dan@upvote.aulinkfedilink1•1 year 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.
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.