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.
-
Show this thread
-
Replying to @pcwalton
The main point of React is to be able to write UI = f(State), so you only think about states, O(n), rather than state transitions, O(n^2). Do you have an idea for achieving that without diffing?
4 replies 0 retweets 10 likes -
Replying to @graue
At some point you have to bottom out and update the state. When you do that, your framework should automatically update the UI at the same time.
1 reply 1 retweet 6 likes -
I don't see how that answers the question. How do you automatically incrementally update the UI without diffing?
1 reply 0 retweets 1 like -
Another way is to mark elements dirty and redo the layout of just what's dirty at a transaction boundary, e.g. the frame rate. My possibly outdated or incorrect understanding is that changing a DOM element forces redoing the layout immediately rather than transactionally.
1 reply 0 retweets 0 likes
It doesn’t. Frame construction is lazy. It does however force layout flush when you do things like query element positions.
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.