virtual-dom

What does Angular 2 use to update the DOM. Is it Shadow DOM or Virtual DOM ? Was there any such concept in Angular 1? Günter Zöchbauer Angular2 doesn't use shadow DOM (default) nor virtual DOM . With encapsulation: ViewEncapsulation.Emulated (default) there is no shadow DOM because style encapsulation is only emulated. encapsulation: ViewEncapsulation.Native enables shadow DOM on browsers that support it natively or it's again emulated when the webcomponents polyfill is loaded. Shadow DOM is also not targeting performance as virtual DOM is, but style encapsulation. Angular2 doesn't use virtual

I'm assuming the virtual DOM, and that React takes care of it with diff'ing. But I had a recruiter say that ref's affect the actual DOM, I can't see how this can be. I assume that they were just mistaken. Refs should reference the actual DOM. One usage of Refs is integrating with third-party DOM libraries, so you can directly modify the DOM using Refs. If Refs reference the virtual DOM, I don't think the demand can be meet. You modify a virtual DOM, but you can't make sure the modification would be synchronized to the actual DOM. Besides, if you want to modify actual DOM when using react, you

"test" is an array of object in my vue data var vue = new Vue({ el: '#content', data: { test: [ { array: [0, 0, 0, 0] }, { array: [0, 0, 0, 0] } ], number: 0 }, methods: { setNumber: function(){ this.number = 5; }, setArray: function(){ this.test[0].array[0] = 9; } } }) Problem is that if i change the value of an element in "array", while log shows that the value has changed, it doesn't update on the page. On the other hand, if i change value of "number", both "number" and "array" value on the page are updated. <section id="content"> <div>Value in array: {{ test[0].array[0] }}</div> <div>Value

Does implementing Shadow DOM in my projects will make them faster like virtual DOM that's used by React? Günter Zöchbauer Virtual DOM Virtual DOM is about avoiding unnecessary changes to the DOM, which are expensive performance-wise, because changes to the DOM usually cause re-rendering of the page. Virtual DOM also allows to collect several changes to be applied at once, so not every single change causes a re-render, but instead re-rendering only happens once after a set of changes was applied to the DOM. Shadow DOM Shadow dom is mostly about encapsulation of the implementation. A single

I saw a React dev talk at http://www.youtube.com/watch?v=x7cQ3mrcKaY and the speaker mentioned that dirty-checking of the model can be slow. But isn't calculating the diff between virtual DOMs actually even less performant since the virtual DOM, in most of the cases, should be bigger than model? I really like the potential power of the Virtual DOM (especially server-side rendering) but I would like to know all the pros and cons. I'm the primary author of a virtual-dom module, so I might be able to answer your questions. There are in fact 2 problems that need to be solved here When do I re