News for hackers. Stuff that matters.
Re:Jiff 1.0: A datetime library for Rust by kbolino on Monday November 16, 2026 @02:19PM (#50521739)
In this particular matter, I can't help but be biased against your perspective due to Go. In that language, the desire to meet the "most common usescases" has led to an IMO pathologically bad attitude towards doing this right. In Rust, only the bare primitives are exposed -- Instant, SystemTime, Duration -- but these are sufficient for others to build better abstractions. Whereas, in Go, all of the primitives are hidden behind a "good enough" (it's not) API, and you have to break out O/S-specific code if you want to do better.
Re:Jiff 1.0: A datetime library for Rust by darksaints on Monday November 16, 2026 @02:36PM (#50521958)
Java had the same problem, but then they then fixed with `java.time`, which I believe should be the benchmark for off-the-shelf date/time functionality. Doing it right absolutely is a management and leadership problem, and management/leadership can fail, but when it is done right the result is so much better than the bazaar of 20 half-baked mutually incompatible solutions.
Re:Jiff 1.0: A datetime library for Rust by kbolino on Monday November 16, 2026 @02:42PM (#50522068)
I don't agree that Java had the same problem. Java has had System.currentTimeMillis() since the beginning, and System.nanoTime() since 2005. Meanwhile, in Go, time.Now().Unix() performs a pointless timezone lookup and time.Since(foo) only uses the monotonic clock if foo has monotonic time, a property of time.Time values that you can't interrogate.
Re:Jiff 1.0: A datetime library for Rust by stouset on Monday November 16, 2026 @03:50PM (#50523063)
The gold standard these days is JavaScript’s Temporal, which Jiff and java.time.temporal are descendants of.
Re:Jiff 1.0: A datetime library for Rust by nick__m on Monday November 16, 2026 @05:44PM (#50524544)
you are wrong on ancestry, java.time is descendant of joda-time and temporal the descendant of a js port of joda-time.