On Tue, Oct 1, 2024 at 2:32 AM Yoav Weiss (@Shopify) <yoavwe...@chromium.org> wrote:
> 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. > About a year ago, we had a thread asking about the standardization plans for this, and I suggested giving TC39 a PSA and trying to standardize this through the Web Perf WG. Can you point to any minutes from TC39 where you discussed this with them, and have you proposed this to a WG as https://www.chromium.org/blink/launching-features/#new-feature-prepare-to-ship:~:text=propose%20that%20the%20feature%20migrate%20to%20a%20working%20group requires? 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? > Yes, but the TAG hasn't commented: https://github.com/w3ctag/design-reviews/issues/947. It's architecturally interesting to convey performance hints via comments, where HTML uses attributes or sometimes elements, and CSS uses properties (e.g. will-change <https://developer.mozilla.org/en-US/docs/Web/CSS/will-change>), but TC39 is probably the right venue to consider that. Jeffrey -- 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/CANh-dXnLhk1D5R%2Bx0%3DFyLqztYsCWNmrTpFc%3DRYix3WAR30ZXJg%40mail.gmail.com.
