realized i started saying “on twitter” referring to the parts i like (that spiritual twitter forks also do) and “on x” to mean the parts i’m not so into
if client react was all about Values, server react is all about References. since react functions are projections, often you don’t need to unwrap a value — you just reference it in the output.
examples: referencing server code on the client, client code on the server, server code from the cache
RE:
this is wild. i love this so much. non-serializable inputs to a cached function (like pieces of JSX with server logic) don’t cause a cache miss because they can only be used transparently (they’re not introspectable so the cached logic couldn’t depend on the actual value anyway)
RE:
ok so based on my testing, if Parent has 'use cache' and takes children then children indeed don’t invalidate it
<child> {/* more dynamic */}
</child>
but like HOW?.... i don’t get it
