3 ms·
There was a post on HN where someone explored the immediate gui paradigm for their PhD (or masters degree, don't remember) and they discovered that this assumpt
by Fire-Dragon-DoL 4y ago
There was a post on HN where someone explored the immediate gui paradigm for their PhD (or masters degree, don't remember) and they discovered that this assumption is actually incorrect, given the interactions and os optimizations the battery usage (well, cpu usage and gpu usage) was lower overall. I remember very little details, it was amazing
- jb1991 4y agoI would have to read it to see what you mean. I cannot imagine a world in which the normal way of doing immediate mode graphics was more efficient than retained mode.
- Fire-Dragon-DoL 4y agoI'm trying hard to find the link, but I'm struggling, sorry. During my researching, a lot of posts point out that "innediate mode" refers to the API, not the implementation, and that React is effectively a hack to obtain an immediate mode gui on top of retained mode. Doesn't say anything about performance, just that the implementation behind the scene can retain state to save battery