9 ms·
How is this different from the dirty checking that Angular does in its ModelView update cycle?
by EGreg 13y ago
How is this different from the dirty checking that Angular does in its ModelView update cycle?
- peterhunt 13y agoThis is copied from a comment of mine on Reddit which should cover it: http://skulbuny.com/2013/10/31/react-vs-angular/ http://skulbuny.com/2013/10/31/react-vs-angular/
- dmak 13y agoThat seemed more like a rant about Angular than an unbiased comparison. I had the impression that the writer didn't do things the "Angular way" when he said, "Since composing directives is so annoying, they end up being basically mini-jQuery apps that are pretty hard to maintain."
- sebmarkbage 13y agoReact does the diffing on the output (which is a known serializable format, DOM attributes). This means that the source data can be of any format. It can be immutable data structures and state inside of closures. The Angular model doesn't preserve referential transparency and therefore is inherently mutable. You mutate the existing model to track changes. What if your data source is immutable data or a new data structure every time (such as a JSON response)? Dirty checking and Object.observe does not work on closure scope state. These two things are very limiting to functional patterns obviously. Additionally, when your model complexity grows, it becomes increasingly expensive to do dirty tracking. However, if you only do diffing on the visual tree, like React, then it doesn't grow as much since the amount of data you're able to show on the screen at any given point is limited by UIs. Pete's link above covers more of the pref benefits.
- Joeri 13y agoSo, maybe i'm misunderstanding, but, the perf advantage is that react waits until the next RAF and then only updates the parts of the DOM that actually changed? So, now i'm wondering: why can't the browser do that? Isn't this whole middle-man approach something to eventually be optimized out?
- polarix 13y agoSure, the browser could implement a virtual dom and then sync it and do a reflow once per frame.
- fbender 13y agoYou can do that with the help of `document.createDocumentFragment()`.
- peterhunt 13y agoThe browser does do this already to an extent. The difference is that React constrains the operations a user can do (i.e. we only give them the DOM node if they explicitly ask for it and only let them manipulate it at certain times) so we eliminate the operations that cause the DOM to be slow. If the DOM were to implement this it'd have to break backwards compatibility.