Rob Palmer
@robpalmer.bsky.social
JavaScript Infrastructure & Tooling at Bloomberg. Co-chairing TC39. Likely to tweet tech stuff about JS & software performance. Opinions are my own.
Both are deprecated.
February 12, 2026 at 5:12 PM
Both are deprecated.
Hello Dave!
Which API resources are you following?
(and why can't I DM you? 😉)
Which API resources are you following?
(and why can't I DM you? 😉)
February 11, 2026 at 10:50 PM
Hello Dave!
Which API resources are you following?
(and why can't I DM you? 😉)
Which API resources are you following?
(and why can't I DM you? 😉)
This looks like it assumes const object bindings imply the values are `as const`-style immutable containers.
Which no other DTS-generator assumes.
Which no other DTS-generator assumes.
February 11, 2026 at 10:44 PM
This looks like it assumes const object bindings imply the values are `as const`-style immutable containers.
Which no other DTS-generator assumes.
Which no other DTS-generator assumes.
Excellent. Thank you for the updated numbers. At a first glance, they now seem credible and broadly make sense.
Is there a write up on how you avoid the need for Isolated Declarations? Are you performing cross-file analysis?
Is there a write up on how you avoid the need for Isolated Declarations? Are you performing cross-file analysis?
February 11, 2026 at 8:03 AM
Excellent. Thank you for the updated numbers. At a first glance, they now seem credible and broadly make sense.
Is there a write up on how you avoid the need for Isolated Declarations? Are you performing cross-file analysis?
Is there a write up on how you avoid the need for Isolated Declarations? Are you performing cross-file analysis?
This is the first rule of benchmark club.
The second rule - more of a courtesy really - is to share the code and results privately with other candidates before any public announcement. It significantly increases credibility if fix ups occur before the claim, rather than iteratively updating later.
The second rule - more of a courtesy really - is to share the code and results privately with other candidates before any public announcement. It significantly increases credibility if fix ups occur before the claim, rather than iteratively updating later.
February 9, 2026 at 1:56 PM
This is the first rule of benchmark club.
The second rule - more of a courtesy really - is to share the code and results privately with other candidates before any public announcement. It significantly increases credibility if fix ups occur before the claim, rather than iteratively updating later.
The second rule - more of a courtesy really - is to share the code and results privately with other candidates before any public announcement. It significantly increases credibility if fix ups occur before the claim, rather than iteratively updating later.
How does the performance compare to TS-Go?
February 9, 2026 at 1:16 AM
How does the performance compare to TS-Go?
All JS features in V8 ultimately make their way to the active Chromium browsers such as Arc, Brave, Edge, Opera, Vivaldi, as well as the active V8 non-browser runtimes such as Node & Deno.
February 7, 2026 at 4:34 PM
All JS features in V8 ultimately make their way to the active Chromium browsers such as Arc, Brave, Edge, Opera, Vivaldi, as well as the active V8 non-browser runtimes such as Node & Deno.