You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PureRenderMixin in React can really help for boosting performance. It avoids diffing some parts of the virtual tree, saving computations. See this demo.
Because this is more related to mechanisms in React's components and not so much in the inner workings of their virtual DOM algorithms, it might not be easy to find an equivalent solution in virtual-dom. But maybe? Has this been tried?
One idea:
I have one back-of-the-envelope idea: to attach the parent data (React's "property") to the VTree, and inside virtual-dom's diff algorithm, it could use that data instead of the whole VTree structure, as a quick diff check prior to the real diff. Maybe we could even use a hash of the data instead of the data itself.
The text was updated successfully, but these errors were encountered:
use key on each element in this list, this will put virtual-dom in re ordering mode instead of diffing mode, this allows for very efficients moves of elements in the list.
PureRenderMixin in React can really help for boosting performance. It avoids diffing some parts of the virtual tree, saving computations. See this demo.
Also see this issue.
Because this is more related to mechanisms in React's components and not so much in the inner workings of their virtual DOM algorithms, it might not be easy to find an equivalent solution in virtual-dom. But maybe? Has this been tried?
One idea:
The text was updated successfully, but these errors were encountered: