3 ms·
well thats what I meant. Basically I'm not a game dev, but keeping simple values on the stack is most often not a problem. However it's insane how many Lists, A
by merb 9y ago
well thats what I meant. Basically I'm not a game dev, but keeping simple values on the stack is most often not a problem. However it's insane how many Lists, Arrays I need and I'm a web developer. So I guess a Game Dev even needs more of these (Inventory, Stats, Chat, whatever)
- Kapura 9y agoYeah, but the big key is to keep things instantiated only once (where reasonable). So, if I'm making an RTS, I keep only one list of selected units, and it persists even if I have no units selected. No reallocation or losing the reference means nothing is getting garbage collected. There are bigger convos to be had about data architecture here, but now's neither time nor place for it.