Thanks all! I'll reply to various things at once: domenic@: thanks for pointing out the wrong link, that was a mistake. There's no Origin Trial feedback summary available, and the results we've gotten from Workspace devs are not publicly available.
jyasskin@: The TC39 info session is scheduled for the upcoming October meeting next week ( https://github.com/tc39/agendas/blob/main/2024/10.md ) Thanks for adding the TAG design review link, too. This is a TAG early design review, not a TAG specification review (I didn't find a way in Chromestatus to enter a link to the early design review; there's only a field for the specification review. Setting the state as "pending" is probably also not right, since that field is probably only about the specification review - fixed that now.) We haven't proposed this to a WG yet, there was discussion about how we go about that and rbyers@ proposed moving that discussion to an I2S, so here it is. miketaylr@: It's very likely that the privacy & security reviews will be very straightforward in comparison to the API owners approval. This is essentially a JavaScript feature (though, not a semantics changing one) so it doesn't have privacy implications. Security-wise, it's much less risky than other V8 features on average, so I don't expect much work to be coming from that direction either. That's why I kicked off the API owner discussion first, since that's the most interesting one. Would it be ok to do the privacy & security reviews only after this discussion has converged? On Wed, Oct 2, 2024 at 5:55 PM Jeffrey Yasskin <jyass...@chromium.org> wrote: > 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 > -- 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/CAED6dUDrcx98wUWWAM4QZS5k%2BBv6_zST8_vMs2Oj5%2BSO6PYayw%40mail.gmail.com.
