A datetime library for Rust
Comments on “A datetime library for Rust”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Jiff 1.0 is a Rust datetime library that puts time zone handling at the center of its API, so common daylight saving time mistakes are harder to make. Its author commits to keeping the 1.0 API stable indefinitely, since other crates are beginning to expose Jiff types publicly.
Why it ranked
No. 23 of 60 with a score of 0.63. The panel rated it highest on technical depth (0.92) and new information (0.92), lowest on audience breadth (0.47). Placed No. 23, No. 24 by score alone: the fifth Programming & dev tools story of the day (−0.040). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- A detailed, well-substantiated tour of a widely used Rust datetime library's 1.0 release with extensive technical content; relevant to builders but a niche tool, not a landmark.
- AI judgeJudge 3gpt-5.6-luna
- A substantial Rust datetime library reaches 1.0 with detailed, practical API coverage, especially around time zones, DST ambiguity, durations, parsing, formatting, and calendrical operations. It is relevant mainly to Rust developers, not most technologists.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.63total under rubric v2.3
- Significance0.50
- Reader interest0.67
- Audience breadth0.47
- Practical relevance0.77
- Substantiated0.86
- Technical depth0.92
- New information0.92
- Counts against: Promotional0.09
- Counts against: Overclaim0.16
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.61 | 0.35 | 0.55 | 0.50 | 0.26 | +0.24 | +0.121 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.60 | 0.70 | 0.72 | 0.67 | 0.12 | +0.26 | +0.175 |
| Audience breadthHow many people who build technology does it concern? | 0.52 | 0.50 | 0.38 | 0.47 | 0.14 | +0.13 | +0.061 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.90 | 0.70 | 0.70 | 0.77 | 0.20 | +0.22 | +0.169 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.87 | 0.80 | 0.92 | 0.86 | 0.12 | +0.05 | +0.043 |
| Technical depthHow technically substantive is it? | 0.99 | 0.90 | 0.86 | 0.92 | 0.13 | +0.05 | +0.046 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.90 | 0.85 | 1.00 | 0.92 | 0.15 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.12 | 0.10 | 0.05 | 0.09 | 0.07 | −0.19 | −0.017 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.25 | 0.15 | 0.08 | 0.16 | 0.17 | −0.11 | −0.018 |
| Sum of contributions | +0.625 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.625 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-16/23/"><img src="https://rubric.hrih.si/badge/2026-11-16/23.svg" alt="Ranked #23 on Rubric, 16 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 5 no source given · 2 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkGeneralization
Jiff has already seen widespread adoption in the Rust ecosystem.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Jiff has already seen widespread adoption in the Rust ecosystem”
The source says No passage could be compared.
Source cited by the article: crates.io/crates/jiff/reverse_dependencies
No source givenVersion
This blog post announces the Jiff 1.0 release.
The article gives no link or citation for it.
The article says “This blog announces the Jiff 1.0 release by giving a tour of its API”
The source says No source to compare with.
No source givenGeneralization
Jiff is used in production in projects including uv, Cargo, Starship, fd, Nushell, mise, Jujutsu, uutils/coreutils and as the basis for a Temporal implementation in AWS LLRT.
The article gives no link or citation for it.
The article says “Jiff is already used in production in many projects: uv, Cargo, Starship, fd, Nushell, mise, Jujutsu, uutils/coreutils and even as the basis for a Temporal implementation in AWS LLRT”
The source says No source to compare with.
Couldn’t checkVersion
A list of breaking changes between Jiff 0.2 and Jiff 1.0 is available in the CHANGELOG.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “To see a list of breaking changes between Jiff 0.2 and Jiff 1.0, please consult the CHANGELOG”
The source says No passage could be compared.
Source cited by the article: github.com/BurntSushi/jiff/blob/master/CHANGELOG.md
Matches sourceNumber
SignedDuration always corresponds to a 96-bit integer number of nanoseconds and can only represent physical time units.
The cited source says the same thing.
The article says “is a signed version of std::time::Duration and always corresponds to a 96-bit integer number of nanoseconds”
The source says “A signed duration of time represented as a 96-bit integer of nanoseconds”
Source cited by the article: docs.rs/jiff/1.*/jiff/struct.SignedDuration.html
No source givenNumber
Jiff's datetime range only extends to +/- 9999, whereas Temporal's range is larger.
The article gives no link or citation for it.
The article says “Jiff’s datetime range only extends to +/- 9999, whereas Temporal’s range is larger”
The source says No source to compare with.
No source givenGeneralization
The author concluded that both chrono and time had reached a local maximum in 2024.
The article gives no link or citation for it.
The article says “I had concluded that both chrono and time (in 2024) had reached a local maximum”
The source says No source to compare with.
No source givenCausal conclusion
Jiff is heavily inspired by Temporal, inheriting its API design, functionality and parsing/formatting of datetime values.
The article gives no link or citation for it.
The article says “Jiff inherits API design, functionality and even parsing/formatting of datetime values”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 8 pts, front page
Recorded for context only, checked 16 Nov 2026, 05:47 UTC. It played no part in the ranking.