Chrome will soon have a way to cache the compilation result of inline scripts (bytecode). Wow!
chromestatus.com/feature/5132...
If you see me in the crowd, feel welcome to say hi!
(I can also invite you to the #WebPerf Slack)
@ricky.fm When you have multiple (unrelated) expensive components running transitions to update, how could you "flush" some transitions individually instead of batching? (apart from making each comp faster to render)
How's the mobile CPU landscape evolving? Thanks to process node improvements, a mid-range Android from 2025 is (finally!) as fast as 2017's iPhone 8, but a low-end (~$100) smartphone isn't yet as speedy as a decade-old iPhone 6s.
Blink: Intent to Prototype: Lazy loading for video and audio elements
I started migrating the main monorepo at @framer.com to @voidzero.dev's oxlint. Speed difference is day and night.
For 420 enabled rules (including typescript-eslint rules), without cache:
eslint: 3m58s | 21 GB RAM
oxlint: 0m46s | 4.6 GB RAM (oxlint) + 6 GB tsgo
🚀5x faster, 2x less RAM usage
#PerfNow has incredibly interesting talks. Anyone who's serious about performance should join.
Proud that we at @framer.com are sponsors.
💫 When performance experts choose WebPerformance Report to simplify and share their insights, it reinforces our mission to make data more actionable for everyone.
Thank you, Jacob @kurtextrem.de, for trusting WPR to bring clarity to web performance. ⚡
👉 webperformancereport.com#Testimonials
#webperf
Belated hi from @perfnow.nl! Come talk to us (me & @kurtextrem.de) about React performance, Framer sites, LCP/INP and more :D
Speeding up the JS ecosystem OXC edition 🚀
We made both oxfmt and oxlint 50% faster on projects with >50k directories.
marvinh.dev/blog/speedin...