New to Immediate Mode (IM) UI and trying to understand something. If all desktop applications rendered their UI in IM aiming at ~60fps+, would not that make them compete for the resources more than needed and overuse them? May I ask @cmuratori to drop a hint?
-
-
Replying to @meglio
"Immediate" refers to the API, not the dispatch. There is no need to continuously redraw the interface if it is not animating.
1 reply 0 retweets 34 likes -
Replying to @cmuratori @meglio
Would you qualify React.js as an immediate mode API? Since the vast majority of the time you don't think of a separate init and update steps. You just say what the UI should like given the current input/state.
2 replies 0 retweets 0 likes -
Replying to @wisam910 @cmuratori
React’s API resembles the one of IM; however, under the hood it still updates the existing DOM rather than generating it “from scratch” (whatever it means for browsers). So in my understanding it looks like IM but it does not act like true IM in terms of its DOM implementation.
2 replies 0 retweets 0 likes -
Replying to @meglio @cmuratori
Yes, and? The question is about the API not the underlying mechanism.
1 reply 0 retweets 0 likes -
Replying to @wisam910 @cmuratori
The whole idea of IM is about building the final UI from scratch, not updating the existing one. So acting as a wrapper and then still updating an old DOM UI doesn’t sound as true IM. That how I understand it.
1 reply 0 retweets 0 likes
No, the idea of IM is that code is more flexible than data for defining an interface, so the interface should be written as code and not data. How it is implemented past the API stage doesn't affect whether I would call it IM or not, much like a GPU driver, etc.
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.