News for hackers. Stuff that matters.
Re:Jiff 1.0: A datetime library for Rust by quodlibetor on Monday November 16, 2026 @01:57PM (#50521423)
I maintained chrono for about half a decade, and the specific reason I took on maintenance was because the API sucked and I hoped I could make it better.

Turns out, the reason people wanted to use it was because the API was stable and every slight step towards improvement was met with... resistance. I stopped maintaining it because the burnout from seeing what it could be and not seeing any path to get there was too much for me.

I'm extremely grateful to burntsushi for writing the datetime library rust deserves. Chrono is stable and is maintained (though semi-deprecated) by an extremely reliable rustacean -- you don't need to leave, but you'll probably be happier if you do.

Re:Jiff 1.0: A datetime library for Rust by burntsushi on Monday November 16, 2026 @01:59PM (#50521448)
<3
Re:Jiff 1.0: A datetime library for Rust by thatsabadlook on Monday November 16, 2026 @09:51PM (#50526787)
Hope you are doing well sushi
Re:Jiff 1.0: A datetime library for Rust by steveklabnik on Monday November 16, 2026 @02:38PM (#50521994)
Thanks for helping maintain Chrono. Burnout is the worst, I hope you're feeling better these days.
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...
Re:Jiff 1.0: A datetime library for Rust by Arch485 on Monday November 16, 2026 @03:57PM (#50523149)
I'm really curious - what makes you say chrono's API sucks?

I've used it in several projects, and to me it seems just fine. Granted, I don't do a lot of cross-time zone work; I exclusively use UTC whenever possible.

Re:Jiff 1.0: A datetime library for Rust by lifthrasiir on Monday November 16, 2026 @06:07PM (#50524869)
A commonly cited reason is that it mixes Option<T> and Result<T, E> for error handling. It was designed well before Rust's API convention is settled, and I also wrongly assumed that some features like procedural macros would be delivered soon (which was why `ymd` and such panic on error).
Re:Jiff 1.0: A datetime library for Rust by joel2oliver on Monday November 16, 2026 @04:16PM (#50523407)
Thanks. I shipped a couple of things on chrono and never had to think about it. That was you.
Re:Jiff 1.0: A datetime library for Rust by ddahlen on Monday November 16, 2026 @04:30PM (#50523571)
Thanks for maintaining such a core tool, it has been really helpful for me!
Re:Jiff 1.0: A datetime library for Rust by thatsabadlook on Monday November 16, 2026 @09:50PM (#50526781)
I am extremely grateful that you maintained chrono. Used it at several companies. Thank you.
Re:Jiff 1.0: A datetime library for Rust by ninkendo on Tuesday November 17, 2026 @10:38AM (#50532844)
[delayed]
Re:Jiff 1.0: A datetime library for Rust by n923263 on Tuesday November 17, 2026 @03:21PM (#50537621)
> You can say "just maintain the older versions too", and that would be absolutely great, if anyone really did this. In practice anything but the most recent major is neglected.

The implication is that you should maintain the old version, if you're still using it. (And if no one is using it, who cares?)

> Improvements that need breaking changes should happen under a new name, with a new project, so that the old project can still exist and receive updates.

And then no one really maintains old projects, either.

Fundamentally, the only difference between "libfoo-1,libfoo-2" and "libfoo,libbar" is that the latter causes more namespace pollution and makes it harder to figure out which successor projects are at least trying to maintain the overall design goals of the previous version.

Re:Jiff 1.0: A datetime library for Rust by ninkendo on Wednesday November 18, 2026 @08:22AM (#50546009)
[delayed]