Thanks for working on this! This is super interesting!! On Monday, September 30, 2024 at 4:12:25 PM UTC+2 Marja Hölttä wrote:
(Sending this I2S as recommended by API owners, to continue the discussion about shipping this feature.) Contact emailsma...@google.com, lesz...@google.com Explainerhttps://github.com/explainers-by-googlers/explicit- javascript-compile-hints-file-based/blob/main/README.md Specificationhttps://explainers-by-googlers.github.io/explicit- javascript-compile-hints-file-based We don't typically ship features with specs on personal or Google-owned repos. I think it would be good to try and move this to an incubation venue (e.g. WICG). This would be a better place from an IPR perspective (i.e. allow contributions outside of Google), and will help us validate that this is something that has at least some industry support. Summary Allow attaching information about which functions should be eager parsed & compiled in JavaScript files. The information will be encoded as magic comments. We'll first target launching the file-based explicit compile hints, and as a follow up, investigate selecting individual functions for eager compilation. Blink componentBlink>JavaScript <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript> TAG review Did you file for a TAG review? TAG review statusPending Chromium Trial NameJavaScriptCompileHintsMagic Link to origin trial feedback summaryhttps://google.qualtrics.com/ jfe/form/SV_9SLyOGnTj2cwo0C Origin Trial documentation linkhttps://docs.google.com/ document/d/19xTAM4A75tz0xUq_velMzGA4JHEgXpyflUxXTcuNiyE/edit?usp=sharing Risks Interoperability and Compatibility No interoperability / compatibility risks. Other browsers are likely to ignore the hints if they perceive they cannot benefit from them. Ignoring the hint is allowed behavior. We plan to make the hints generic though, so that other browsers can later start to support them too, e.g., if they implement background parsing / compilation. *Gecko*: N/A (https://github.com/mozilla/standards-positions/issues/780) *WebKit*: N/A (https://github.com/WebKit/standards-positions/issues/172) *Web developers*: Positive Positive signals from partners who want to use compile hints to eager-compile core JS files. *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? Debuggability Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?No The feature doesn't trigger any functional changes and cannot be tested by WPT. Flag name on chrome://flags Finch feature nameNone I *think* you can put JavaScriptCompileHintsMagicRuntime <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/runtime_enabled_features.json5;l=2462?q=JavaScriptCompileHintsMagic%20-f:out&ss=chromium&start=11> as the feature name. Non-finch justificationNone Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=13917 Estimated milestonesOrigin trial desktop first115Origin trial desktop last 117Origin trial extension 1 end milestone131 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). Link to entry on the Chrome Platform Statushttps://chromestatus.com/ feature/5100466238652416?gate=5172761812533248 Links to previous Intent discussionsIntent to Experiment: https://groups. google.com/a/chromium.org/g/blink-dev/c/BmN1Wus8V1s/m/3L2uU-wGAgAJ Intent to Extend Experiment 1: https://groups.google.com/ u/1/a/chromium.org/g/blink-dev/c/mwZYYTBJ12g/m/HWsRCkuxAQAJ This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- Google Germany GmbH Erika-Mann-Straße 33 80636 München Geschäftsführer: Paul Manicle, Liana Sebastian. Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Diese E-Mail ist vertraulich. Falls sie diese fälschlicherweise erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail an die falsche Person gesendet wurde. This e-mail is confidential. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/95883282-a93f-4b2a-b34f-9bd4c401129en%40chromium.org.
