this post was submitted on 27 Oct 2025
33 points (100.0% liked)

Programming

23557 readers
94 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

Or: XKCD 1179 has its heart in the right place, but we can only wish it was actually that simple

top 5 comments
sorted by: hot top controversial new old
[–] cgtjsiwy@programming.dev 12 points 3 weeks ago

This is missing the biggest difference: ISO 8601 costs 190-450€, whereas RFC 3339 is free.

[–] lukalix98@programming.dev 6 points 3 weeks ago (1 children)
  • We need a new standard that unifies all 14 standards.
  • Proceeds to create a new standard
  • There are 15 standards.
[–] joyjoy@lemmy.zip 4 points 3 weeks ago

The only way to fully unify all 14 standards is to support all 14 standards.

[–] palordrolap@fedia.io 4 points 3 weeks ago

TIL that, at least according to the linked page, YYYY-MM-DD hh:mm:ss (or %Y-%M-%D %h:%m:%s in strftime format) isn't valid in either system.

ISO8601 apparently disallows spaces altogether, so that space should be a T for it to qualify there; RFC3399 allows the space, but insists there should be a UTC offset of some kind at the end.

Unrelatedly, the page's use of %Z and %z doesn't match with strftime formatting at all, so there's at least one other standards problem lurking here.

[–] billygoat@catata.fish 2 points 3 weeks ago

This has the “just one more bro” feel to it.