Jiff 1.0 puts time zones at the heart of Rust datetime handling

Jiff 1.0: A datetime library for Rust

BurntSushi releases Jiff 1.0, a Rust datetime library built to make daylight saving time and time zone handling central to its API rather than an afterthought. Already used in production by uv, Cargo, Starship, fd, Nushell, and Jujutsu, it layers civil dates and times, timestamps, and time zones into a ZonedDateTime, with explicit strategies for resolving ambiguous times during folds and gaps. The author commits to API stability indefinitely so Jiff can serve as a public dependency.

My own belief is that the difficulty comes from poor modeling of the domain. Instead of encapsulating the complexity inside a reusable bundle of code, many datetime libraries pass some or all of the complexity on to its users.
  1. quodlibetor

    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.

  2. Dagonfly

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

  3. mgrandl

    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.

  4. ddahlen

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

  5. the__alchemist

    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.

More from this day

2026-11-16