Temporal_rs Is Here! the Datetime Library Powering Temporal in Boa and V8
Key topics
The Boa team announces the release of Temporal_rs, a datetime library powering Temporal in Boa and V8, marking a significant milestone towards shipping Temporal in Chrome unflagged, with the community expressing excitement and appreciation for the team's hard work.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
27m
Peak period
3
0-1h
Avg / period
2
Key moments
- 01Story posted
Sep 24, 2025 at 11:35 AM EDT
3 months ago
Step 01 - 02First comment
Sep 24, 2025 at 12:02 PM EDT
27m after posting
Step 02 - 03Peak activity
3 comments in 0-1h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 25, 2025 at 3:02 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
On the integration with Kiesel and Chrome, I'm pleased to see that engines/browsers can share the cost of developing new language features. Temporal is massive! Almost as big as the delta of introducing ES6. There are 4,000+ tests. The functionality does not need to be engine-specific, so it makes sense to leverage reuse.
I believe this is the first introduction of Rust into V8 itself. Which seems like a happy side-effect that hopefully makes it easier to share more Rust libraries in future. This helps keep browser development sustainable.
My only concern is that temporal_rs packages it's own time zone data, which may make the WASM package a little heavy, so I've been inclined to leave the polyfill up to fullcalendar's implementation.
Also, Diplomat supports traits and callbacks so you could actually make the timezone impl pluggable. Though we don't currently have JS support for that.
But also tz info isn't that big I think...