News for hackers. Stuff that matters.
Re:Jiff 1.0: A datetime library for Rust by lifthrasiir on Monday November 16, 2026 @03:02PM (#50522354)
As the original author of Chrono, thank you so much for your service. It was always a learning experience for me to design and maintain Chrono (that's why the API is not very good, despite my best efforts) and I too had been burnt out from doing so, so it was fortunate that the right people stepped up and kept the torch burning for so long time.
Re:Jiff 1.0: A datetime library for Rust by the__alchemist on Monday November 16, 2026 @04:46PM (#50523762)
Thanks to you both. I am giving benefit of doubt to those saying Jiff is even better, and I am trying Jiff today, but make no mistake: Chrono is by far, the best datetime library I've used. If Jiff ends up being people's #1, I hope they realize that Chrono is probably the #2 of any datetime library in existance. Thank you so much. It is dramatically better than Python's and JS's (official and unofficial) ones. I can rely on it for std and embedded tasks, and trust it to act as I expect.
Re:Jiff 1.0: A datetime library for Rust by BrandoElFollito on Monday November 16, 2026 @06:01PM (#50524770)
Why is it so much better than, say, Arrow?
Re:Jiff 1.0: A datetime library for Rust by the__alchemist on Monday November 16, 2026 @06:43PM (#50525231)
Arrow has no date type. No time type either! Using their recommended approach of "use datetimes for everything" is a poor representation of data in many scenarios and leads to surprise behavior. Chrono's sins, as enumerated in the Jiff documents, aren't on the same tier.

Unless you're talking about Arrow, the Apache Parquet interface library in either Python or Rust - that's a different matter; great software!

Re:Jiff 1.0: A datetime library for Rust by BrandoElFollito on Tuesday November 17, 2026 @04:47AM (#50529386)
I am trying to find a case where a time without a date would be useful. The only one I can think about are analog monotonic clocks.

In any other case I can think of, you need to attach the time to a date and a timezone. You can display it bare in the context of the viewer (who has an implicit or explicit timezone and time reference) but any manipulation without these will not end well.

Would you have some examples for the poor representation of data and surprise behaviour?

Re:Jiff 1.0: A datetime library for Rust by the__alchemist on Tuesday November 17, 2026 @07:14AM (#50530375)
What datetime is your birthday? What time is your Monday alarm clock set for?

There are so many, and sometimes Arrow/Moment's abstraction is OK. Other times it's awkward as it overconstrains. Sometimes it has surprising behavior.

Re:Jiff 1.0: A datetime library for Rust by GoblinSlayer on Wednesday November 18, 2026 @05:02AM (#50544263)
>What datetime is your annual birthday celebration?

Doesn't that belong to a scheduler library?

Re:Jiff 1.0: A datetime library for Rust by quodlibetor on Monday November 16, 2026 @06:33PM (#50525142)
I shouldn't have used the word sucked -- personal jargon that I use all the time to describe my own code and try not to apply to other people's -- it was created pre-1.0 and we learned a lot as a community in the 10 years you spent building it.

Thank you so much for building something that was obviously good enough to sustain the community for 12 years <3

Re:Jiff 1.0: A datetime library for Rust by hermitdev on Monday November 16, 2026 @06:49PM (#50525292)
As someone who has worked with implementing date/time functionality before, I'm empathize. Getting APIs "right" is hard, and getting it wrong is easy because there's so many ways to get it wrong. Especially when you start getting into something like handling something like daylight saving time, which is inherently political and changes arbitrarily over time. I've spent most of my career in finance. I distinctly remember near shouting matches over what it meant to add "1 day" to a datetime. Does it mean adding 24 hours? Or, does it mean give me the same time of day tomorrow? What happens if tomorrow is the other side of a DST change? These seems like trivial questions, but matter if you're talking about, say physical delivery of oil or gas at a set rate per hour.
Re:Jiff 1.0: A datetime library for Rust by democracy on Monday November 16, 2026 @07:30PM (#50525734)
I learnt not to say "shit code" in public since quite often the history would point at my changes after investigation lol
Re:Jiff 1.0: A datetime library for Rust by masklinn on Tuesday November 17, 2026 @04:37AM (#50529329)
Honestly it’s the best case of having called something shit code, it means you’ve improved enough to recognise its faults, and at most you’re hurting your own feelings and nobody else’s.
Re:Jiff 1.0: A datetime library for Rust by lifthrasiir on Monday November 16, 2026 @07:43PM (#50525841)
I'm fine, actually. There is a joke that every successful programming language creator would spend next decades fixing faults in one's language. I feel that applies to every successful software as well...