3 ms·
Better graphics code does mean what I'm on about. It's about removing any triggers for GC, which means removing allocations. If you're blocking your UI thread
by fidotron 12y ago
Better graphics code does mean what I'm on about. It's about removing any triggers for GC, which means removing allocations.
If you're blocking your UI thread with deallocating a giant graph of doom then you have other problems. Deferring pauses, however, is not a realistic option.
- mike_hearn 12y agoI was referring to the triple buffering, full use of GL for rendering and better vsyncing when I talked about graphics changes, not GC stuff. That was separate and also makes things smoother but it's unrelated. Deferring pauses is quite realistic for many kinds of UI interaction and animation. If your animation is continuous/lasts a long time and requires lots of heap mutation then you need a good GC or careful object reuse, but then you can run into issues with malloc/free too. But lots of cases where you need something smooth don't fit that criteria.