2 ms·
I would love to see a reference for the "profound practical difference well-recognized in the decades of work that's gone into memory GC". Many languages, incl
by saurik 15y ago
I would love to see a reference for the "profound practical difference well-recognized in the decades of work that's gone into memory GC".
Many languages, including Objective-C (although, arguably/mostly Foundation), manage to provide primitives that make it easy to manage either at once; the only high-level complexity you have to give up is cycle detection, which is a serious problem and "known tradeoff" in many fields, including deadlock detection (hence, why I mention an interesting connection to things like CAP).
Also, I would also love to see a reasonable program that does not have external resources: I find that almost all the work my programs are doing are managing and moving around external resources... from threads to sockets to money, you are probably not doing anything terribly useful unless you are dealing with a non-memory resource.
Regardless, the goal of these statements is "a defense of Objective-C", not "why Objective-C is amazing": the "defense of Java", when you show someone a four-level nested try/finally whose sole purpose is to make non-deterministic finalization of File objects exception-safe, is "but we have garbage collection, which has these nifty properties, including automatic cycle detection".
- pvg 15y ago>I would love to see a reference for the "profound practical difference well-recognized in the decades of work that's gone into memory GC". I don't think you need a reference - when we discuss algorithms we have a notation to describe an algorithm's behaviour in time and space yet never bicycle messengers. If anything, this suggests these resources are, indeed, somehow (and obviously) more fundamental. The 'defense of Obj-C' article thing is pretty silly, no argument there.