@cmuratori In short @reactjs rerenders everything each frame and uses IDs to match up state. Same basic idea as IMGUI, works splendid.
-
-
Replying to @BrandonBloom
@cmuratori biggest difference in@reactjs is that rendering returns partial/shallow scene graph (html/dom) instead of side effecting render.1 reply 0 retweets 0 likes -
Replying to @BrandonBloom
@cmuratori engine of@reactjs is "lazy" when recursively (re-)rendering, committing a minimal diff to browser dom as if it were a gfx card1 reply 0 retweets 1 like -
Replying to @BrandonBloom
@BrandonBloom@reactjs I feel like most people deeply misunderstand IMGUI, unfortunately :(1 reply 0 retweets 0 likes -
Replying to @cmuratori
@BrandonBloom Glancing at@reactjs at the moment, I would say that it does not look like a particularly good implementation of IMGUI.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@BrandonBloom@reactjs I'd have to spend more time looking at it to be certain but it looks like it has the same typical misunderstandings.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@reactjs I think you're reacting too quickly to 1) the OOP veneer that makes it palatable and ...1 reply 0 retweets 0 likes -
Replying to @BrandonBloom
@cmuratori@reactjs 2) your own misunderstandings of the challenges presented by the (deeply flawed) browser dom1 reply 0 retweets 0 likes -
Replying to @BrandonBloom
@cmuratori@reactjs the fundamental approach matches up: externalize state, identify widgets by id, rerender from source data, etc1 reply 0 retweets 0 likes -
Replying to @BrandonBloom
@cmuratori@reactjs big departure is that gfx cards have usable imperative drawing API, browsers do not, so add 1 new idea: lazy draw calls3 replies 0 retweets 1 like
@BrandonBloom @reactjs I am not confused :)
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.