Remix.run Logo
▲ the__alchemist an hour ago

I will give this a shot, however... Rust is the only language I've used where I want to use the established one, chrono. I will roll my own in JS, for example, or begrudgingly use or wrap the python.datetime one (And not touch the third party python ones which do awful things inspired by Moment.js like conflating dates , times, and datetimes, under the guise dates and times don't have use on their own), but Chrono actually is comparatively nice (S-tier relative to others), both std and no_std.

▲masklinn an hour ago | parent | next [-]

> I will roll my own in JS

Hopefully Safari will soon have temporal implemented and we can leave that behind (it's in 27.3b so not out of the question).

> Chrono actually is comparatively nice

burntsushi has written pretty extensively about:

1. comparisons to existing datetime libraries (https://docs.rs/jiff/latest/jiff/_documentation/comparison/i...), chrono's original author also commented (https://github.com/BurntSushi/jiff/issues/63)

2. why they felt it was a good idea to write a new library (https://docs.rs/jiff/latest/jiff/_documentation/design/index...)

3. why they didn't wish to contribute to either chrono or time (https://docs.rs/jiff/latest/jiff/_documentation/design/index...)

And as randomblock linked, chrono is deprecating itself.

▲the__alchemist 41 minutes ago | parent [-]

Ty for the details! That is about as clear as anyone could hope!

This is still very surprising given the context; if the top datetime library of any language is getting soft-replaced with something nicer, woe be to those in other languages!

▲randomblock1 an hour ago | parent | prev [-]

Chrono is deprecated: https://github.com/chronotope/chrono/issues/1768

I found switching to Jiff from Chrono quite easy.