Blog post: https://v8.dev/blog/explicit-compile-hints
Status page: https://chromestatus.com/feature/5100466238652416
Sr. Performance Engineer @Framer · webperf/UX/security
Blog post: https://v8.dev/blog/explicit-compile-hints
Status page: https://chromestatus.com/feature/5100466238652416
Chrome 136+ ships a new V8 version that supports a "compile hint", which makes V8 parse and compile all functions in that file eagerly.
Great for entry points – where you know all functions will very likely be used. Less so as 'one weird trick to make all your JS faster'.
@eeeps @matthiasott @kevinpowell @mdn @grigs Afaik, chromium might introduce a DPR cap, but I can't think of any reasonable change to how the source is selected that could break the mechanism.
Anyway, I certainly agree, if you can use picture, you should - I think I mention that somewhere in the post too. Less complexity, easier to handle.
In my scenario, we couldn't switch for various engineering related reasons so I came up with this 😄
@matthiasott @kevinpowell @mdn @eeeps @grigs
You can get pretty clever with the img tag alone though as I demo here: https://kurtextrem.de/posts/modern-way-of-img. Using <picture> is much simpler, though.
🎉 Framer can now simulate DOM sizes and positions on the server, without the real DOM.
This lets us automatically do optimizations that rely on element sizes – like loading=lazy, image preloading*, and content-visibility*.
AFAIK no other site platform supports this today.
(* = soon)
Last week in Framer performance: we shipped AVIF support! Now, all images are served as AVIF, making them 20+% smaller.
AVIF takes ages to encode, tho, so we came up with a clever trick. 🧵
@nolan Good point!
@sarajw @Schepp @tunetheweb @developers I'd prefer English by default too (unless article has been translated to a specific language by a human)
@eeeps Love the article. Just shared it on the WebPerf slack (are you on it btw?)
@Yoav Congratulations!! Exciting to hear what you'll be working on. eCom is a big topic for WebPerf! Happy to hear that you'll stay involved in WebPerfWG.
@stefan Done. I really wonder why.
Responsive & performant images are complicated. My first #webperf article really goes in-depth on `<img srcset>` and provides a unique alternative to `<picture>` 📸
If you've learned something new, I'm happy about boost's & your feedback :)
@TheRealNooshu link doesn't work for me just fyi