1918
2023-08-09.jpg
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Aug 2023
1918 points (93.2% liked)
Memes
45754 readers
1208 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
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.”
Whenever I’m passing a date from a website backend to frontend I’ll usually send it inside something like
<span>then have JavaScript convert it to a string based on the browser’s localization settings.So many websites I see for error reporting, etc always throw everything out as UTC and it drives me crazy. It would be nice to just have an HTML tag for ISO-8601 (or even UNIX as done here).
Your prayer has been answered! Hear ye:
https://www.w3schools.com/tags/tag_time.asp
That looks like it’s only useful for machine-readable dates so it wouldn’t be useful for killing off the JavaScript portion of my “hack.” I cry at night for this
Looks like my code example glitched here. Basically a an HTML span tag with some CSS class for JavaScript to process.