Frontend

A good reminder that the amount of client-side JavaScript code you ship can make or break a website’s user experience (and people’s mobile data bills) in places with less than state-of-the-art internet infrastructure.

Streaming bits of client-side JavaScript in response to user interaction using a framework like Qwik (or Astro) is a key advantage here.

A good reminder that the amount of client-side JavaScript code you ship can make or break a website’s user experience (and people’s mobile data bills) in places with less than state-of-the-art internet infrastructure.

Streaming bits of client-side JavaScript in response to user interaction using a framework like Qwik (or Astro) is a key advantage here.

https://youtu.be/M6lGKtA37uE

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

i love optimizations. i’ve done a lot to compress as much as i can om the front side of things for frames.sh now consuming less than 5~6mb for the total package on initial load, the rest cached on the client side to rehydrate on updates. i should do more on the back end side of things. i’m a sucker for snappy page loads.

Love to see it. This industry could do with more bundle-conscious web developers like you 🫡

5-6 still seems kinda heavy. What does the library load look like?