Tentative conclusion after being burned in performance too many times: Diffing (like in React, but by no means is this unique to React) is a sign that there's something wrong with your framework design.
-
-
I've mostly ended up relying heavily on diffing in contexts where I want things to be pretty fast, but they're not truly performance critical. I think a lot of UI work has this flavor.
-
The upside of diffing is it let's you express your code in state oriented terms, which really does make things easier to reason about.
- 2 more replies
New conversation -
-
-
But React is solving another problem: free the programmer from worrying about what are the necessary incremental updates when the state changes. Diffing makes it possible without degraded performance, but performance is secondary.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Git treats diffing as an optimization and only applies it if conditions are met. I have suspected for a while now that this is why git succeeded.
-
This Tweet is unavailable.
- 12 more replies
New conversation -
-
-
Despite how much I enjoy using React, its use of diffing has always been slightly off-putting, it's nice to see I'm not the only one. I wonder if someday there will be another framework with the same benefits, without needing diffing.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Without claiming a complete understanding of their usage in Haskell et al, I'm starting to think that diff/patch is a loosely defined lens, which is where attention should go.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.