3 ms·
I don't know about you, but I appreciate that I don't have a garbage collector with coding for mobile apps (Not done any for OSX apps yet). You'll know what I m
by nubela 14y ago
I don't know about you, but I appreciate that I don't have a garbage collector with coding for mobile apps (Not done any for OSX apps yet). You'll know what I mean if you work with large images (Bitmaps) in Android, then you'd wish you have a better craft at release memory (instead of recycle())
- stcredzero 14y agoI am wondering when someone will implement a good Ulterior Reference Count or an Age-Oriented GC for iOS/OS X. These are both hybrids of GC and reference counting that combine the strengths of both. Basically, new objects tend to die quickly, so the overhead of reference counting is generally redundant, and GC techniques like copying collectors tend to excel. Old objects tend to stick around, so reference counting overhead is low. By using a hybrid of both techniques where they are strong, you avoid a lot of overhead: pointless ref-count changing, and pointless scanning of object graphs. The result is something with the high throughput of generational GC with only a fraction of the maximum pause time. https://researchers.anu.edu.au/publications/29505 https://researchers.anu.edu.au/publications/29505 http://www.cs.technion.ac.il/~erez/Papers/ao-cc.pdf http://www.cs.technion.ac.il/~erez/Papers/ao-cc.pdf
- jballanc 14y agoI think anyone who thinks that GC/Memory Management is a "solved" problem hasn't been paying attention! Oh, and thanks for the links!