Bob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 10 months agoEveryday, as an Americanmidwest.socialimagemessage-square18fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageEveryday, as an Americanmidwest.socialBob@midwest.social to Lemmy Shitpost@lemmy.worldEnglish · 10 months agomessage-square18fedilink
minus-squaredan@upvote.aulinkfedilinkarrow-up0·10 months agoSome ISO8601 formats are good, but some are unreadable (like 20240607T054831Z for date and time).
minus-squarezqwzzle@lemmy.calinkfedilinkEnglisharrow-up0·10 months agoThe ones without separators tend to be for server/client exchange though.
minus-squaredan@upvote.aulinkfedilinkarrow-up1·10 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.
ISO8601 gang
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.