When I rolled one a long long time ago, it just transparently retained a cache, and GC'd stuff not referenced in the previous k-frames
-
-
It was retrofitted on; the API interface was still immediate-mode. Since I didn't have fancy animations, k==1
1 reply 0 retweets 0 likes -
Interesting. If you look at it a certain way a cache is arguably retained mode under the hood though…
1 reply 0 retweets 0 likes -
Well of course the library is often retaining data (when you edit a text field it is retaining cursor/selection etc.)
2 replies 0 retweets 0 likes -
Yeah, this is the interface/implementation confusion I was referring to
1 reply 0 retweets 0 likes -
Pragmatically I think the hypothetical most-optimized imgui would probably be slower than hypothetical most optimized rmgui
1 reply 0 retweets 0 likes -
But we are mostly aiming at programmer efficiency, analoguous to comparing, say C to C#
1 reply 0 retweets 0 likes -
Yeah. And GUI performance is definitely about avoiding dumb things, not to-the-metal levels of performance
1 reply 0 retweets 1 like -
By nature of being presented to the user most UI also have a natural upper limit of content size/complexity
1 reply 0 retweets 0 likes -
Modern web (I assume you may be coming from that background) are maybe the worst case in term of UI cost/complexity
1 reply 0 retweets 2 likes
Yup. (I wrote most of Servo’s layout.) In our case layouts are frequently 50ms+ due mostly to text and interaction with text
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.