引用此（）article
DOM是否会瓶颈那些导致重绘的东西？如果是这样，那么React的虚拟DOM渲染的效果应该不会像重绘整个组件一样（在一次浏览器API调用中）？我认为浏览器执行的算法只会尝试重绘diff从一个状态到另一个状态（比如git也许？）。暗示浏览器本身维护一个虚拟DOM。那么，创建一个虚拟DOM有什么意义？
还应该添加一个具有显示样式的元素设置为 none 的属性不会严重影响性能？我会自己分析一下，但是我不知道到哪里去了，因为我最近才开始使用javascript编程。 解决方案
对于SO来说有点宽泛，但作为一般的答案，来自同一篇文章的其他引文也非常相关：
虚拟DOM的作用是计算DOM的一种状态与下一个状态之间的差异，最小化DOM中的DOM更新非常聪明的方式。
所以：
与其他几个具有虚拟DOM的工具/库相同）。
更多关于虚拟DOM的内容及其优点。
Quoting this (https://news.ycombinator.com/item?id=9155564) article
Are the DOM bottlenecks only those things that cause a redraw? If so then shouldn't one render from React's virtual DOM amortize to the same performance as redrawing an entire component (in one browser API call of course)? I would think that the algorithms executed by the browser only try and redraw the diff from one state to another (like git maybe?). Implying that the browser maintains a virtual DOM by itself. So then what is the point of having a virtual DOM?
Also should adding an element that has the display style property set to none not be affecting performance badly? I would profile this myself but I do not know where exactly to turn as I started javascript programming only recently.
This question may be somewhat broad for SO, but as a general answer, some other quotes from the same article are also very relevant:
What react's virtual DOM does, is calculate differences between one state of the DOM and the next state and minimizes DOM updates in a very smart way.
So:
And the react engine does just that (same as several other tools/ libraries with a virtual DOM).
More info on what virtual DOM is and its advantages e.g. here.
这篇关于React.js如何加速使用虚拟DOM进行渲染的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！