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:00 is WAY more human legible than 1691696733.
2023-08-10 15:45:33-04:00
1691696733
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.”
Your 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:00
is 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.”
Your prayer has been answered! Hear ye:
https://www.w3schools.com/tags/tag_time.asp