Skip to content

Commit 1742a3f

Browse files
Update index.md
1 parent b58db37 commit 1742a3f

File tree

1 file changed

+8
-9
lines changed
  • blog/2025-09-24-temporal-release

1 file changed

+8
-9
lines changed

blog/2025-09-24-temporal-release/index.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,7 @@ interested in learning more about small implementation details.
2323

2424
Currently, `temporal_rs` v0.1 is being used by Boa, [Kiesel][kiesel-site],
2525
[V8][v8-site], and [Yavashark][yavashark-repo] for their Temporal
26-
implementations (more on that later) and will soon being
27-
[shipping in Chrome](https://chromestatus.com/feature/5668291307634688).
26+
implementations (more on that later) and is [estimated](https://chromestatus.com/feature/5668291307634688) to land unflagged in Chromium v143.
2827

2928
### Why v0.1? Why not v1.0?
3029

@@ -50,18 +49,18 @@ culminated in an absolutely massive PR,
5049
[#3277](https://github.com/boa-dev/boa/pull/3277) (ASIDE from nekevss:
5150
mea culpa).
5251

53-
> _Temporal is the single biggest addition to ECMAScript since ES6_
52+
> _"Temporal is the single biggest addition to ECMAScript since ES6"_
5453
5554
The PR itself stubbed out a lot of the methods, implemented some
5655
Duration and Instant functionality, and started the support for custom
57-
calendars. There were, however, 2 major take aways from this PR, first:
58-
- Temporal is a massive specification update, it's the single biggest addition to ECMAScript since ES6; and second..
59-
- there is a lot of room to potentially optimize Temporal if we do not deal with
56+
calendars. There were, however, 2 major take aways from this PR:
57+
- Temporal is a massive specification update, it's the single biggest addition to ECMAScript since ES6.
58+
- There is a lot of room to potentially optimize Temporal if we do not deal with
6059
`JsValue` directly.
6160

62-
After a couple weeks, the question came up amongst maintainers of not just Boa, but other engines:
63-
could we separate the datetime logic and implementation off into a completely
64-
separate library? Sure, why not.
61+
After a couple weeks, the question came up amongst maintainers of not just Boa, but also V8:
62+
"_could we separate the datetime logic and implementation off into a completely
63+
separate library?_" Sure.
6564

6665
The first commit of then `boa_temporal` occurred in PR
6766
[#3461](https://github.com/boa-dev/boa/pull/3461), which moved the

0 commit comments

Comments
 (0)