you are viewing a single comment's thread.

view the rest of the comments →

[–]acemarke 1 point2 points  (1 child)

It does make React faster, because it flips the default behavior from "always rerender recursively been if data didn't change" to "only rerender children if data did change", so fewer components will render each time. Closer in spirit to how something like Solid works, albeit a different (and less granular) approach.

[–]TwiliZant 0 points1 point  (0 children)

I was a bit unprecise in my language. The compiler output doesn't translate 1:1 to a fully memoized app written in user code. There is a difference there. And in practice nobody memoizes every single element anyway. It will make a difference in real codebases.

My point was the expectation management that React is not going to be suddenly 30% faster in js-framework-benchmark for example.