Yes, the time crate was rebooted after 0.1 and got a new maintainer.
I think we're starting to do better again with Chrono, hopefully it won't take us too long to get out a solid 0.5 release.
(I'm one of the current Chrono maintainers -- the previous maintainer burnt out on the project earlier this year, at which point the project sorely needed some TLC.)
Do you think there's any possibility of `time` and `chrono` merging at some point? (or one depending on the other and providing a superset of functionality). It's rather confusing having two de-facto datetime libraries in the Rust ecosystem, and as far as I can see there isn't any major difference in philosophy or scope between the two libraries?
One depending on the other seems like the worst of both worlds: more code to compile for everyone.
Personally I still prefer chrono's API; chrono is also much more conservative about the MSRV (currently at 1.38) whereas time consistently bumps to N - 3, which seems like a meaningful difference.
time depends on the libc timezone parsing with some fairly involved workarounds to avoid hitting undefined behavior, while we incorporated time zone parsing in Rust with some caching for chrono.
So I think these are meaningful differences -- feels unlikely that these projects will merge.
I think we're starting to do better again with Chrono, hopefully it won't take us too long to get out a solid 0.5 release.
(I'm one of the current Chrono maintainers -- the previous maintainer burnt out on the project earlier this year, at which point the project sorely needed some TLC.)