you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 3 days ago (6 children)

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

  • source
  • parent
  • hideshow 6 child comments
  • [–] 6 points 2 days 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 2 days ago (2 children)

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 days ago (1 child)

    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
  • hideshow 1 child comment
  • [–] 1 point 2 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.

  • source
  • parent