kurtextrem.de
Senior Performance Engineer @Framer · The INP optimization guy · webperf/UX/security · @kurtextrem on other platforms.
27 posts
746 followers
329 following
Regular Contributor
Active Commenter
comment in response to
post
The "Performance" tab of DevTools shows compilation & parsing here - important: disable caching to avoid v8's byte cache!
The compile hint changes how early the compilation happens. If the main thread stalls while waiting for compilation to finish, the compile hint can have positive impact.
comment in response to
post
An easy way to figure out if this might make sense to add for you: Open Chrome DevTools -> 3 dots -> More tools -> Coverage. The files with the least amount of unused functions right after a page load, will gain the most from this.
comment in response to
post
Blog post: v8.dev/blog/explici...
Status page: chromestatus.com/feature/5100...
comment in response to
post
anytime! :)
comment in response to
post
Sorry to hear that, Barry. My thoughts are with you and your family
comment in response to
post
That said, you can build SPAs with both.. but it doesn't really matter, because the takeaway *should* be you (as a react user) should pay attention to use more of what react offers to achieve good INP - and not "react is bad".
A bold headline draws attention to that. Happy to hear feedback though.
comment in response to
post
I disagree with this take. See the library measurements from Ariakit. They don't involve any site navigation whatsoever.
The important part is React offers utilities to have great UX & INP, but not enough people use it (yet). So it's the knowledge part that is missing in my opinion.
comment in response to
post
I'll defer that to @tunetheweb.com, but personally I disagree with the data I have. Page navigations rarely have any bad INP unless you synchronously re-render the full page without fetching data. @danielroe.dev held a talk about how e.g. Nuxt suffered & fixed this.
comment in response to
post
sorry, I hope my comparison didn't trip anyone's feet (that wasn't the intention). My intention was to bring attention to INP & React. I also mention it's not only react, but also other frameworks that perform worse than the average
comment in response to
post
INP doesn't differentiate between CSR and SSR.
comment in response to
post
Part 2 of my "How to improve INP" series is for library authors and devs working on React codebases.
We'll take a look at how to:
✨ Ensure great INP & UX after user interactions
🚀 Make hydration concurrent
💡 Get non-blocking useEffects, always
so that... your site outperforms jQuery instead.
comment in response to
post
yes: typescript-eslint.io/rules/return... with the option "in-try-catch"
comment in response to
post
Tagging also @addyosmani.bsky.social and @mths.be, as e.g. I know some info in this article: v8.dev/blog/cost-of... is also outdated by now (the streaming thresholds for example). Do we have any public docs regarding script streaming that have info on how it works in Chromium & Node in 2024?
comment in response to
post
Let's see! Happy to stand corrected (at least for more recent versions of chrome/V8, I suppose?)
comment in response to
post
likewise! looking forward to chatting to you in the future :)
comment in response to
post
that's an awesome idea
comment in response to
post
Damn it's been some time since we had an invite link 👀 we should have printed that on a QR
comment in response to
post
Half of the WebPerf slack too 😄🤝🏼
comment in response to
post
oh yeah, that's on point!
comment in response to
post
what would be needed for react support?
comment in response to
post
Cool stuff! I think Marvin also published this here: github.com/denoland/pre...
so... both is useable for plain React, right?