Jiff 1.0: A datetime library for Rust

(burntsushi.net)

117 points | by burntsushi 1 hour ago

15 comments

  • ddahlen 35 minutes 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...

    • burntsushi 33 minutes 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/
      • ddahlen 24 minutes 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.

  • mgrandl 59 minutes 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.
    • dicke 45 minutes ago
      He is incredibly kind and gracious too. I've made some contributions to jiff, and Andrew is so easy to work with.
  • kjuulh 11 minutes ago
    Jiff is very nice to work with. It is always a pleasure working with something crafted by burntsushi
  • the__alchemist 40 minutes 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.
  • pbrowne011 33 minutes 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

  • poulpy123 52 minutes ago
    I would have expected a modern language to have an extensive datetime library in its standard library
    • lambda 19 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.

    • dminik 45 minutes 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.
      • darksaints 12 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.
    • solidsnack9000 44 minutes 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.

    • tredre3 48 minutes 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.
      • afdbcreid 14 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.

    • sunshowers 43 minutes ago
      A poorly designed one, maybe. My understanding is that the Temporal model is a very recent invention.
  • robrain 21 minutes ago
  • fstephany 59 minutes 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!

  • Sparkle-san 56 minutes ago
    > Jiff is pronounced like “gif” with a soft “g,” as in “gem.”

    Woah now, let's not get too controversial.

    • MadameMinty 1 minute ago
      Out of pure spite, I will pronounce Jiff like "gif", with a hard "g", as in "good".
    • dmit 53 minutes ago
      The man's name is "burnt sushi". I suspect he's fine with controversy. :)
  • gosen 33 minutes ago
    I thought it's the right moment to finally do something with Rust, but I work on my "J" pronunciation first
  • PowerElectronix 29 minutes ago
    Weird, you can't ever pronounce Jiff as gif.
  • brianwitte 49 minutes ago
    the jiff pronunciation meta got my brain working hard for second. love it
  • NetOpWibby 46 minutes ago
    Love seeing the correct pronunciation of gif
  • jheriko 10 minutes ago
    [dead]
  • bitbasher 51 minutes ago
    [flagged]