Post

Cool to see #MDN exploring a unique #frontend architecture which better meets their needs. developer.mozilla.org/en-US/blog/m... #web #JavaScript

A lot of the core ideas here are stuff I've been trying to formalize in #HydroActive and #rules_prerender. Islands of reactivity on a mostly static page and driving resource loading by what gets rendered are both key features most FE systems lack.

#HydroActive supports deferring upgrade / lifecycle hooks until the component is interacted with, solve load ordering so your dependencies are always upgraded, and manages dependencies on components so they are hydrated exactly when they need to be and no earlier. github.com/dgp1130/Hydr...

I do like MDN's post as a great case study of the benefits of investing in your build process. You often aren't designing a website, so much as a process which *will generate* a website. You should care about your build process just as much as the actual client code you're shipping.

Indeed, that's where we wrong with with CRA in the past - the Webpack config was originally abstracted away, and then (once ejected) overly complex and generic. We nearly made the same mistake with the rewrite, where our prototype was using Rsbuild - the batteries included sibling of Rspack.