Jacob "kurtextrem" Groß
@kurtextrem.de
Senior Performance Engineer @Framer · The INP optimization guy · webperf/UX/security · @kurtextrem on other platforms.
@mmocny.com we talked about this at a dinner 2y? ago. Chromium doesn't collect how many people turn off JavaScript if I remember correctly, right?
November 1, 2025 at 6:57 PM
@mmocny.com we talked about this at a dinner 2y? ago. Chromium doesn't collect how many people turn off JavaScript if I remember correctly, right?
Time to change that! Maybe if you tell some of your Vercel colleagues how great it is, it might happen next year?
October 31, 2025 at 1:16 PM
Time to change that! Maybe if you tell some of your Vercel colleagues how great it is, it might happen next year?
More people from the big frameworks should join! @danielroe.dev was here last year, which was awesome too. Would love to have someone from React's team here at some point :)
October 31, 2025 at 12:04 PM
More people from the big frameworks should join! @danielroe.dev was here last year, which was awesome too. Would love to have someone from React's team here at some point :)
CJS is for sure at least one culprit: github.com/sxzz/rolldow...
GitHub - sxzz/rolldown-plugin-require-cjs: Transform ESM imports to CJS requires when the imported module is pure CJS
Transform ESM imports to CJS requires when the imported module is pure CJS - sxzz/rolldown-plugin-require-cjs
github.com
October 28, 2025 at 12:44 PM
CJS is for sure at least one culprit: github.com/sxzz/rolldow...
I used this for some project after benchmarking: www.npmjs.com/package/turb... - caveat: that was years ago, before V8 has speedup json.parse this year
www.npmjs.com
October 9, 2025 at 2:46 PM
I used this for some project after benchmarking: www.npmjs.com/package/turb... - caveat: that was years ago, before V8 has speedup json.parse this year
as he's writing to head, there shouldn't be any cost/invalidation?
October 5, 2025 at 11:27 AM
as he's writing to head, there shouldn't be any cost/invalidation?
Shouldn't be `rAF(async () => { await scheduler.yield(); triggerScripts() })` more efficient in this case?
I'm not seeing anything in triggerScripts that makes it needed to run in a rAF, but maybe I'm missing the obvious
I'm not seeing anything in triggerScripts that makes it needed to run in a rAF, but maybe I'm missing the obvious
October 5, 2025 at 10:32 AM
Shouldn't be `rAF(async () => { await scheduler.yield(); triggerScripts() })` more efficient in this case?
I'm not seeing anything in triggerScripts that makes it needed to run in a rAF, but maybe I'm missing the obvious
I'm not seeing anything in triggerScripts that makes it needed to run in a rAF, but maybe I'm missing the obvious
Why the double rAF in the observer callbacks?
October 4, 2025 at 8:53 PM
Why the double rAF in the observer callbacks?
Me too. Great improvement to the perf debugging experience in react :)
October 2, 2025 at 6:34 AM
Me too. Great improvement to the perf debugging experience in react :)
I'm not using Redux so I can't tell if wrapping the returned value & memo'ing the returned nodes is possible in your case, but this works even with Suspense boundaries inside the children: bsky.app/profile/kurt...
I don't have a sandbox, but we're using it on prod @ Framer.
September 27, 2025 at 9:17 AM
I'm not using Redux so I can't tell if wrapping the returned value & memo'ing the returned nodes is possible in your case, but this works even with Suspense boundaries inside the children: bsky.app/profile/kurt...
bsky.app/profile/kurt...
you can kinda make it concurrent during hydration with this
you can kinda make it concurrent during hydration with this
I don't have a sandbox, but we're using it on prod @ Framer.
September 27, 2025 at 9:12 AM
bsky.app/profile/kurt...
you can kinda make it concurrent during hydration with this
you can kinda make it concurrent during hydration with this
does anyone have a quick "I unfortunately missed it"-summary for me?
September 27, 2025 at 9:10 AM
does anyone have a quick "I unfortunately missed it"-summary for me?
Fair point, I agree.
I guess the solution is to write blog posts / talk about that, so React-based frameworks pick it up or people use it if they see a need. I'm saying that because I haven't seen such a solution in the wild before.
I guess the solution is to write blog posts / talk about that, so React-based frameworks pick it up or people use it if they see a need. I'm saying that because I haven't seen such a solution in the wild before.
September 18, 2025 at 2:02 PM
Fair point, I agree.
I guess the solution is to write blog posts / talk about that, so React-based frameworks pick it up or people use it if they see a need. I'm saying that because I haven't seen such a solution in the wild before.
I guess the solution is to write blog posts / talk about that, so React-based frameworks pick it up or people use it if they see a need. I'm saying that because I haven't seen such a solution in the wild before.
Yeah, that's a solution I thought about too. But if you compare that to other FWs like Angular or Astro, they have this natively integrated
September 18, 2025 at 11:26 AM
Yeah, that's a solution I thought about too. But if you compare that to other FWs like Angular or Astro, they have this natively integrated