Right, but not all of it. The way Qwik serializes it is (this is from memory and probably overly simplistic, but conceptually approximate): - Primitives alread

Right, but not all of it. The way Qwik serializes it is (this is from memory and probably overly simplistic, but conceptually approximate): - Primitives already present from the server render are serialized directly into the HTML, and the compiled code reads those values from the DOM - Everything else is split into fine grain chunks, assigned a special identifier (Qwik uses URLs) which is serialized to the HTML to fetch (which can be eager or on-demand) and activate interactivity as needed My understanding is that currently Qwik serializes more than necessary—i.e. can be optimized further to eliminate non-interactive chunks from consideration—but that they’re focused on reducing JS cost first.