3 ms·
> manipulating DOM objects without tricky state machine ... was always faster than with it. You miss the point of VDOMs. VDOMs aren't so much about performance
by anonytrary 8y ago
> manipulating DOM objects without tricky state machine ... was always faster than with it.
You miss the point of VDOMs. VDOMs aren't so much about performance as they are about ease of development and automatically maintaining tree consistency. No one disputes the fact that creating templates and diffing them against the DOM adds overhead compared to writing out the equivalent instructions manually. The point is that nobody wants to write out imperative spaghetti for complex applications.
- baybal2 8y ago> The point is that nobody wants to write out imperative spaghetti for complex applications. You really don't have to, you just have to walk out of that "wood of popular notions." There are libs to handle functionality of any part of a modern MVC app: reactivity, input handling, declarative components, templating... that don't even making you think of manually manipulating the DOM tree.