Reposted by ellemedit
the original mechanism was added here github.com/facebook/rea...
it effectively means that if SA receives some object and returns the same object within the response, it’s encoded as a reference (“argument number 3”) rather than serialized directly.
“use cache” memoization holes fall out of that
it effectively means that if SA receives some object and returns the same object within the response, it’s encoded as a reference (“argument number 3”) rather than serialized directly.
“use cache” memoization holes fall out of that
[Flight Reply] Encode Objects Returned to the Client by Reference by sebmarkbage · Pull Request #29010 · facebook/react
Stacked on #28997.
We can use the technique of referencing an object by its row + property name path for temporary references - like we do for deduping. That way we don't need to generate an ID...
github.com
May 2, 2025 at 10:06 AM
the original mechanism was added here github.com/facebook/rea...
it effectively means that if SA receives some object and returns the same object within the response, it’s encoded as a reference (“argument number 3”) rather than serialized directly.
“use cache” memoization holes fall out of that
it effectively means that if SA receives some object and returns the same object within the response, it’s encoded as a reference (“argument number 3”) rather than serialized directly.
“use cache” memoization holes fall out of that
+1, which article overwhelmed you?
April 16, 2025 at 3:29 AM
+1, which article overwhelmed you?
Reposted by ellemedit
I am once again begging everyone to read this article whenever core web vital comparisons are made web.dev/articles/vit...
How SPA architectures affect Core Web Vitals | Articles | web.dev
Answers to common questions about SPAs, Core Web Vitals, and Google's plan to address current measurement limitations.
web.dev
December 4, 2024 at 2:22 PM
I am once again begging everyone to read this article whenever core web vital comparisons are made web.dev/articles/vit...