this post was submitted on 12 Dec 2023
623 points (95.1% liked)

Memes

45135 readers
1367 users here now

Rules:

  1. Be civil and nice.
  2. 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
[email protected]
[email protected]
[email protected]
[email protected]
623
Standards shouldn't be behind a paywall (lemmy.world)
submitted 9 months ago by [email protected] to c/[email protected]
100 comments fedilink hide all child comments
 
  • ISO 8601 is paywalled
  • RFC allows a space instead of a T (e.g. 2020-12-09 16:09:...) which is nicer to read.
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 9 months ago (1 children)

IMO, ISO 8601 is better for computers, people working with multiple time zones, or critical logging.

RFC 3339 is better used colloquially, while still remaining unambiguous for the use cases that most people use dates and times in.

[–] [email protected] 4 points 9 months ago (1 children)

I'd rather have an explicit time zone any time a datetime is being passed around code as a string. Communicating it to a human is relatively safe since even if there's a mistake, it's directly visible. Before that last step, incorrect time zone parsing or implicit time zone assumptions in code that was written by "who knows" in the year "who knows" can be really annoying.

[–] [email protected] 1 points 9 months ago

I couldn’t agree more!