some per improvements I've been thinking about for choo: safe mutable references for state and using webworkers for threaded UI rendering
-
that's cool. All UI rendering? I have found serialisation overhead too high to make WW worth it for many tasks.
yeah but possibly state mutation too - I've got little experience using WW but keen to figure out what we can do
-
-
cool. I think they are kind of flawed bc the biggest gain should be with big state data, but serialising that is slowish.
-
awesome for complex computation on data that is already resident, tho.
End of conversation
New conversation -
-
-
State mutation could possibly be enough to blow the frame budget, probably best to put it all in there.
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.