you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 15 hours ago (11 children)

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

  • source
  • hideshow 11 child comments
  • [–] 5 points 12 hours ago (5 children)

    Wait, what?! Chrono is phasing out? Shit.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 5 points 6 hours ago (2 children)

    First I heard of it too, I had a look around and yea.. Looks like jiff is the new one to use.

    https://github.com/chronotope/chrono/issues/1768

    I was worried that I'd see jiff was written by one person using AI but it actually looks like it has a decent variety of actual people contributing. I feel OK with having to move across in my projects eventually.

    https://github.com/BurntSushi/jiff

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 4 hours ago (1 child)

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

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 43 minutes 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)

  • source
  • parent
  • [–] 2 points 9 hours ago (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 6 points 8 hours 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

  • source
  • parent
  • [–] 2 points 4 hours 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.

  • source
  • parent
  • [–] 1 point 4 hours ago* (last edited 3 hours 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.

  • source
  • parent