Samsy@lemmy.ml to Memes@lemmy.ml · edit-21 year ago2023-08-09.jpglemmy.mlimagemessage-square345fedilinkarrow-up12.07K
arrow-up12.07Kimage2023-08-09.jpglemmy.mlSamsy@lemmy.ml to Memes@lemmy.ml · edit-21 year agomessage-square345fedilink
minus-squaregravitas_deficiency@sh.itjust.workslinkfedilinkEnglisharrow-up71·1 year agoNah man. Use 8601 for everything. They’re intrinsically chronologically sortable.
minus-squaregravitas_deficiency@sh.itjust.workslinkfedilinkEnglisharrow-up15·1 year agoIn a programmatic context? Sure. In an “I want to be able to comprehend this by glancing at it” context: absolutely not. 2023-08-10 15:45:33-04:00 is WAY more human legible than 1691696733.
minus-squareorangeboats@lemmy.worldlinkfedilinkarrow-up8·1 year agoWhat, you don’t remember your time in Unix timestamps? Filthy casuls.
minus-squareborstis@lemm.eelinkfedilinkarrow-up2·1 year agoIt’s super easy arithmetic too, just remember ”Pi seconds is a nanocentury.”
minus-squareFeathercrown@lemmy.worldlinkfedilinkEnglisharrow-up3·edit-21 year agoYour prayer has been answered! Hear ye: https://www.w3schools.com/tags/tag_time.asp
Nah man. Use 8601 for everything. They’re intrinsically chronologically sortable.
Or unix epoch time
In a programmatic context? Sure.
In an “I want to be able to comprehend this by glancing at it” context: absolutely not.
2023-08-10 15:45:33-04:00is WAY more human legible than1691696733.What, you don’t remember your time in Unix timestamps? Filthy casuls.
It’s super easy arithmetic too, just remember ”Pi seconds is a nanocentury.”
deleted by creator
Your prayer has been answered! Hear ye:
https://www.w3schools.com/tags/tag_time.asp
deleted by creator
deleted by creator