Hacker News Reader

Both Golang (official time package) and Rust (Chrono) have built in tools for dealing with RFC 3339 but not for RFC 8601. IIRC I read about issues with ambiguity in RFC 8601 not present in RFC 3339, and again IIRC Python had issues round-tripping dates because of this.

View on HN

It's ISO 8601, not RFC 8601 (which is `Message Header Field for Indicating Message Authentication Status`).

In fairness, it's doubtful that either Go's or Rust's time-handling facilities would implement support for an email auth header.

Interesting. This is the first time I'm even hearing of RFC 3339. ISO 8601 is just taken for granted everywhere... languages, tools and services (databases, etc).

Admittedly I've not worked with Golang or Rust, and my Python has been limited to scripting more than developing.

Almost everything that claims to implement ISO 8601 actually implements RFC 3339 instead.

I think a lot of people assume ISO 8601 just means 2023-08-31 / 2023-08-31T14:55:30Z.. if only

Reply on news.ycombinator.com