118 points burntsushi 1 hour ago 31 comments
fstephany 1 hour ago | parent
Thank you for your work on this burntsushi!
mgrandl 1 hour ago | parent
dicke 45 minutes ago | parent
Sparkle-san 57 minutes ago | parent
Woah now, let's not get too controversial.
poulpy123 52 minutes ago | parent
tredre3 48 minutes ago | parent
afdbcreid 15 minutes ago | parent
Documentation certainly has nothing to do with it.
Other factors you mentioned are more convincing.
dminik 46 minutes ago | parent
darksaints 12 minutes ago | parent
solidsnack9000 45 minutes ago | parent
For a systems programming language, Rust is relatively easy to write applications in -- but I suspect standard library choices (and other choices) will be driven by the systems side for the foreseeable future.
sunshowers 43 minutes ago | parent
masklinn 22 minutes ago | parent
Temporal does improve some things (it has more strict zoning / less defaults, and improves serialization through RFC 9557), but some of the divergences are not necessarily improvements and rather divergences of opinion (e.g. java.time wilfully made non-ISO calendars second-class, Temporal makes them first class more like Joda, and it's one of the things Colebourne — the lead author of Joda and java.time — strongly disagrees with[1], but the Temporal authors have pretty compelling reasons for it[2]).
[1] https://blog.joda.org/2009/11/why-jsr-310-isn-joda-time_4941... https://github.com/tc39/proposal-temporal/issues/5 https://github.com/tc39/proposal-temporal/issues/1454
[2] https://tc39.es/proposal-temporal/docs/calendar-review#why-a...
vips7L 14 minutes ago | parent
lambda 20 minutes ago | parent
The alternative is to keep a relatively small standard library, and a good package manager, to make it easier for people to iterate on API design in third party packages. Major version changes in a single library can have much less impact accross the ecosystem than standard library packages. Eventually you may get a de facto standard, and sometimes they are then later incorporated into the standard library.
This model isn't without its downsides; it can sometimes mean fragmentation when standardization would help, sometimes these de facto standard libraries can become important enough that they run into the same ecosystem fragmentation issues on major releases. But it allows for more flexibility.
The latter model is what the Rust project decided on for everything outside of the most fundamental time types. Dates and times and timezones are notoriously hard to model in code, and easy to create API designs that are full of footguns, so this is a place where that extra freedom to iterate was more important than standardizing on an API early on.
That iteration has led to a number of different libraries, including time, chrono, and now jiff, allowing for exploring the space of API design to really get it right rather than being stuck with what was available early on.
brianwitte 49 minutes ago | parent
NetOpWibby 46 minutes ago | parent
the__alchemist 40 minutes ago | parent
randomblock1 36 minutes ago | parent
I found switching to Jiff from Chrono quite easy.
masklinn 30 minutes ago | parent
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 6 minutes ago | parent
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!
ddahlen 36 minutes ago | parent
Time is such a pain, I write code for simulating orbits of asteroids/stuff in the solar system, and time and time conversions play a major roll in it. I often need accuracy at the mega-year to giga-year scales, but also sometimes micro-second relative.
I saw on this page that you at least mention TAI time, how are you handling time scales in general? Like would it be hard to add some other timescales like UT1?
Right now I have to do all of this manually and I have been using chrono as just a convenience wrapper so that my users can convert ISO time strings into my internal representation.
Edit: Oh no! I just found out chrono is being semi-deprecated, looks like I'm going to be switching...
burntsushi 34 minutes ago | parent
ddahlen 24 minutes ago | parent
Ah yeah hifitime, I tried it out but its internal representation doesn't work well for my long term simulations, the integer representation ends up increasing the numerical noise in my simulations when I do really sensitive long term ones.
gosen 34 minutes ago | parent
pbrowne011 33 minutes ago | parent
[1] https://docs.rs/jiff-tzdb/latest/jiff_tzdb/#data-generation
PowerElectronix 29 minutes ago | parent
robrain 21 minutes ago | parent
kjuulh 11 minutes ago | parent