Jiff 1.0: A datetime library for Rust
157 points by burntsushi 3 hours ago | 38 comments

quodlibetor 29 minutes ago
I maintained chrono for about half a decade, and the specific reason I took on maintenance was because the API sucked and I hoped I could make it better.

Turns out, the reason people wanted to use it was because the API was stable and every slight step towards improvement was met with... resistance. I stopped maintaining it because the burnout from seeing what it could be and not seeing any path to get there was too much for me.

I'm extremely grateful to burntsushi for writing the datetime library rust deserves. Chrono is stable and is maintained (though semi-deprecated) by an extremely reliable rustacean -- you don't need to leave, but you'll probably be happier if you do.

reply
burntsushi 27 minutes ago
<3
reply
Dagonfly 32 minutes ago
> When should I use Jiff? Jiff isn’t always the right thing to use.

I really appreciate when a project calmly acknowledges that it's not the right tool for every use case, and is not trying to be. That's professional engineering.

Especially in the AI-age, the crucial skill will be what NOT to implement.

reply
mgrandl 2 hours ago
It’s so good like all the other burntsushi libs. Really hope it will be adopted more and more by the wider ecosystem over chrono and co.
reply
dicke 2 hours ago
He is incredibly kind and gracious too. I've made some contributions to jiff, and Andrew is so easy to work with.
reply
ddahlen 2 hours ago
This looks interesting!

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...

reply
burntsushi 2 hours ago
Jiff only supports the Unix time scale. It sounds like you probably want `hifitime` instead! I believe it was designed with your use case in mind. See: https://docs.rs/hifitime/
reply
ddahlen 2 hours ago
Thanks for making useful tools!

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.

reply
the__alchemist 2 hours 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.
reply
masklinn 2 hours ago
> 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.

reply
the__alchemist 47 minutes ago
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!

reply
randomblock1 2 hours ago
Chrono is deprecated: https://github.com/chronotope/chrono/issues/1768

I found switching to Jiff from Chrono quite easy.

reply
poulpy123 2 hours ago
I would have expected a modern language to have an extensive datetime library in its standard library
reply
lambda 60 minutes ago
The problem with this model is that then you try to build all of the libraries that you anticipate users are going to need in one big go before you release version 1 of you language. Because you're trying to do a lot at once, they don't ask get the proper attention they deserve. Then, because of stability guarantees, you're stuck only making backwards compatible changes in the future (or you risk either constant breaking changes, or big changes where a lot changes at once forking the ecosystem, like Python 2 to 3). So if you made any mistakes in the library, you're stuck with them, only being about to deprecate but never really remove them.

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.

reply
dminik 2 hours ago
Any modern language recognizes that some things are inherently complex and will always have tradeoffs that certain users won't be satisfied with and that will be locked in forever. Such modern languages then let users pick whatever approach they actually need by implementing sensible package management.
reply
darksaints 53 minutes ago
A default standard encompassing the most common usecases is a completely reasonable approach. Having a date/time library in the standard library does not preclude other libraries, it just makes it the default and keeps ecosystem integration sane. Not to mention the massive potential reduction in supply chain attacks.
reply
kbolino 8 minutes ago
In this particular matter, I can't help but be biased against your perspective due to Go. In that language, the desire to meet the "most common usescases" has led to an IMO pathologically bad attitude towards doing this right. In Rust, only the bare primitives are exposed -- Instant, SystemTime, Duration -- but these are sufficient for others to build better abstractions. Whereas, in Go, all of the primitives are kept hidden behind a "good enough" (it's not) abstract API, and you have to break out O/S-specific and/or unstable code if you want to do things better.
reply
masklinn 14 minutes ago
Having a date/time library in the standard library actually makes it very difficult for other libraries to take off, and when it's deeply deficient (which is generally the case, turns out time is quite hard) it's actively detrimental to users of the ecosystem, both because it's hell to use and because it teaches them to do things incorrectly. Which then makes an innovative library have a harder time take off, because they need to fix most of their possible users.
reply
solidsnack9000 2 hours ago
I'm not sure this makes sense for a systems programming language -- but I can see it for an application programming language.

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.

reply
tredre3 2 hours ago
Rust doesn't even have an async runtime in its standard library, despite async being part of the language. They believe increased reliance on third party dependencies is better for the ecosystem. Things like supply chain risks or disparate documentation or conflicting dependencies or enormous .cargo are seen as less of a problem than having a built-in API that could go stale one day.
reply
afdbcreid 55 minutes ago
As I've said in other places, supply chain risks have nothing to do with things not being in std, only with them not being official - and things can be (and are) official without being included in std.

Documentation certainly has nothing to do with it.

Other factors you mentioned are more convincing.

reply
sunshowers 2 hours ago
A poorly designed one, maybe. My understanding is that the Temporal model is a very recent invention.
reply
masklinn 2 hours ago
In fairness, Temporal largely follows the model originally defined by Joda, and refined in java.time. So I'd say that Java is probably one of the few languages with a well designed datetime library in the standard library.

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...

reply
vips7L 54 minutes ago
I really enjoy working with java.time. It's one of the best additions to the standard library.
reply
pbrowne011 2 hours ago
Nice! I appreciated the documentation for tzdb on avoiding embedding and the thought process behind using "rearguard" data [1]. Some related GitHub issues are also worth reading [2] [3].

[1] https://docs.rs/jiff-tzdb/latest/jiff_tzdb/#data-generation

[2] https://github.com/BurntSushi/jiff/issues/278

[3] https://github.com/BurntSushi/jiff/issues/279

reply
barchar 18 minutes ago
I do wish they could use the system database on windows. Windows does maintain this data, but it's not in the same format.

The C++ date-time library goes and loads the system copy of ICU (which is updated via windows update) and pulls the tz data from ICU's calendar api.

reply
kjuulh 52 minutes ago
Jiff is very nice to work with. It is always a pleasure working with something crafted by burntsushi
reply
fstephany 2 hours ago
Jiff will probably be the default datetime library for a lot of Rustaceans (and LLMs) in the years to come.

Thank you for your work on this burntsushi!

reply
Sparkle-san 2 hours ago
> Jiff is pronounced like “gif” with a soft “g,” as in “gem.”

Woah now, let's not get too controversial.

reply
dmit 2 hours ago
The man's name is "burnt sushi". I suspect he's fine with controversy. :)
reply
MadameMinty 42 minutes ago
Out of pure spite, I will pronounce Jiff like "gif", with a hard "g", as in "good".
reply
flufluflufluffy 41 minutes ago
if I ever use this lib i'm gonna be scowling with this in the back of my mind the whole time xD

Graphics Interchange Format. Guh-raphics. GIF

reply
gosen 2 hours ago
I thought it's the right moment to finally do something with Rust, but I work on my "J" pronunciation first
reply
robrain 2 hours ago
reply
brianwitte 2 hours ago
the jiff pronunciation meta got my brain working hard for second. love it
reply
the__alchemist 33 minutes ago
With how my brain pronounces short names and acronyms etc vs the commonly-accepted ones, this one has to be something like like "Geth".

> Jiff is pronounced like “gif”

This would have been a hilarious line if he left off the second part!

reply
PowerElectronix 2 hours ago
Weird, you can't ever pronounce Jiff as gif.
reply
NetOpWibby 2 hours ago
Love seeing the correct pronunciation of gif
reply
jheriko 51 minutes ago
[dead]
reply