Bob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 7 months agoEveryday, as an Americanmidwest.socialimagemessage-square298fedilinkarrow-up11.3Karrow-down145
arrow-up11.25Karrow-down1imageEveryday, as an Americanmidwest.socialBob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 7 months agomessage-square298fedilink
minus-squaredan@upvote.aulinkfedilinkarrow-up2·6 months agoSome ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
minus-squareShardikprime@lemmy.worldlinkfedilinkarrow-up1arrow-down1·6 months agoI mean I like this one without the separations
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up5·6 months agoThe ones without separators tend to be for server/client exchange though.
minus-squaredan@upvote.aulinkfedilinkarrow-up1·6 months 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).
I mean I like this one without the separations
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.