• chrash0@lemmy.world
    link
    fedilink
    arrow-up
    20
    ·
    7 days ago

    Jiff is pronounced like “gif” with a soft “g,” as in “gem.”

    shots fired!

    seriously, tho, i hope this is the last datetime library. it’s stupid that there are 3 to choose from at this point, and chrono was super entrenched for it to just deprecate itself seemingly out of nowhere. not helping me convince the Java devs at my company to adopt Rust

        • Kissaki@programming.dev
          link
          fedilink
          English
          arrow-up
          2
          ·
          6 days ago

          Quoting the relevant part:

          The API design for these crates is quite dated, revising it would be a lot of effort, and with jiff there is now an alternative I feel comfortable recommending.

      • BB_C@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        6 days ago

        It will continue to work as before. It’s not like it’s going to disappear or anything 😄

        • chrash0@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          6 days ago

          not exactly. if you’re just using it standalone you can continue to do so. however, many libraries are downstream consumers of chrono, so if you have a dependency on one of those it would be best to move to whatever they replace it with (jiff does seem to be the “blessed” successor)

          • BB_C@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            6 days ago

            it would be best

            The path of least resistance maybe. But as long as you get access to the timestamp (since epoch) from whatever detetime type used, you can do whatever you want. You can even use a third crate if you prefer. It’s neither a big deal, nor does it take that much effort to do.

            And the timestamp is the only data you need on the wire to serialize for most use-cases, except for the few where you need to track time-zone changes alongside the timestamp.

    • FizzyOrange@programming.dev
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      7 days ago

      Yeah I agree. Another one that pissed me off is bincode, a super simple library that I was using that was archived seemingly for no reason. As far as I can tell the author moved it to Codeberg for AI reasons (pointless but whatever), someone though it was a bit suss because they did it with unknown usernames or something, asked about it, and then the author had a hissy fit about “doxing” and rage quit.

      There are some maintained forks, but… come on. This is definitely an argument for a bigger standard library. Or at least more crates controlled by the Rust foundation, so when their authors suddenly quit we can pass maintainership to someone else in an orderly safe way.

      • SorteKanin@feddit.dkOP
        link
        fedilink
        arrow-up
        7
        ·
        6 days ago

        This is definitely an argument for a bigger standard library.

        I mean jiff is a really good argument for a small standard library. Imagine if chrono was in the standard library and this came out and the std date time stuff had to be deprecated… That’d be shit

      • BB_C@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        6 days ago

        This is definitely an argument for a bigger standard library.

        bincode is not the best at anything, which is why people should have, and many indeed did move on from it many years ago.

        It’s not particularly superfast (like speedy/borsh), doesn’t cover zero-copy use-cases, isn’t a standard (like cbor), and even serde support is gone in v2.

        So it’s actually yet another example of why those things SHOULDN’T be in the standard library.

      • Kissaki@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 days ago

        A source move to Codeberg wouldn’t really explain anything changing in regards to Cargo, though, right?

        I agree that collectives or official community collectives could improve a lot of things. It needs additional governance, moderation, and auditing, though. The Rust project is big and funded enough that they could do it. CI and Cargo control can remain in the hands of the governed collective.

    • onlinepersona@programming.dev
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      6 days ago

      Was somebody paying the chrono dev? Was it a passion project? If so, then they owed nobody nothing and it’s the way things are.