The V8 JS language launch process is deprecated, use Blink Intents instead

10 views
Skip to first unread message

Michael Hablich

unread,
Apr 25, 2019, 10:23:08 AM4/25/19
to Michael Hablich Hablich, Adam Klein, sshr...@chromium.org, mat...@chromium.org
Hi folks,
as of now, please do not use the old V8 JS language launch process for launching new JS features. Please use the Blink intent process instead, if you want to develop WebAssembly and JavaScript language features. More information and details can be found here.

Why this change? 
The old V8 JS language launch process was created in a world before the revisited Blink intent process. Nowadays, besides JavaScript also WebAssembly is supported by V8. As a lot of WebAssembly-focused features are not only implemented in V8 but also in Chromium, V8's own Feature Launch Process was not adequate enough. Thus, for WebAssembly features the Blink-intent process is already used. In order to remove process complexity (and ambiguity) V8 is deprecating its own Feature Launch Process and fully adopt Blink-intent for JS features too.

Does this affect non-language features?
No, only features that change the Web Platform API need to follow Blink intents.

If you have any questions, please feel free to get in touch with me.

Cheers,
Michael

Michael Hablich

unread,
May 13, 2019, 3:27:55 AM5/13/19
to Michael Hablich Hablich, Adam Klein, Shruthi Sreekanta, mat...@chromium.org
FYI, there were some small changes around the TAG review requirements:

"For smaller JavaScript or WebAssembly features, a TAG review is not required, as TC39 and the Wasm CG already provide significant technical oversight. If the feature is large or cross-cutting (e.g., requires changes to other Web Platform APIs or modifications to Chromium), TAG review is recommended."

The docs were updated accordingly.

Cheers,
Michael
Reply all
Reply to author
Forward
0 new messages