Got it. I’m saving this post

That’s the point 😂

More from Zach here:

That shift will likely require bundlers & compilers to work more closely together, enabling smarter cross-module optimization. The tournament for faster builds may eventually give way to a more meaningful contest measured not in developer wait times, but in the performance users actually experience.

Bloated JavaScript is still very much a user problem, meaning that the real trophy isn’t faster builds; it’s smaller artifacts, less unused code, and bundles that don’t punish end users with sluggish page loads.

In this @redmonk.com post, I argue that given how much time developers waste waiting for builds, the investment is reasonable, but there’s an irony here. Huge amounts of energy have gone into improving DevX, while the actual runtime performance of what ships to the browser remains an afterthought.

Exactly. Well, as a lame 1/2 measure here’s Lee’s response to @frankspin.bsky.social, which is what your question made me think of

You might find Lee’s responses to the question of why he’s sticking with React/ Next on X may be illuminating for this question

Thanks for this, @brianleroux.bsky.social. Part of me also wanted to link Knut Melvær’s conversation on X, but that felt wrong lol

Thanks for sharing, @joedrumgoole.com!

“Coat bath” 💀