3 ms·
> 1) Re-rendering of virtual DOM content (#1 is your JS code.) Virtual DOM isn't even a real thing. Its some fiction from React. It is really unfortunate to
by austincheney 7y ago
> 1) Re-rendering of virtual DOM content (#1 is your JS code.)
Virtual DOM isn't even a real thing. Its some fiction from React. It is really unfortunate to see the standard layer bloated to compensate for the shortcomings of some framework.
None of the benefits provided by this concept seem necessary, as in these same capabilities and performance solutions were already there by other means.
- tyingq 7y agoReact's docs seem honest about "virtual dom" just being a copy of the dom in memory.
- _bxg1 7y ago> It is really unfortunate to see the standard layer bloated to compensate for the shortcomings of some framework. That's not remotely what's happening. You could have the same issues with (and use this API on) a jQuery-mutated DOM.
- austincheney 7y agojQuery is also not the DOM.
- nicoburns 7y agoThe point is that this attempts to fix performance issues with the DOM itself. These are present regardless of whether you are using abstractions on top of the DOM or not. And in fact, the existence of these perf problems with the DOM is one of the reasons for the creation of vdom layers.
- austincheney 7y agoWhat performance issues? The DOM executes in the browser at near assembly speed. Example: https://news.ycombinator.com/item?id=22321333 https://news.ycombinator.com/item?id=22321333