On Apr 26, 2014, at 10:57 AM, Jens Alfke <j...@mooseyard.com> wrote: > > Yes, there are mainstream garbage-collected platforms now like Android and > .NET. Guess what, in those you also have to spend time baby-sitting memory > management, when you diagnose why your app’s heap size explodes during some > operation or other. Then you get to fool around with weak-references or > object caches or other hacks to try to avoid allocating objects faster than > the GC can clean them up. (I have seen people on mailing lists complain that > they want to be able to manually release/deref/free objects instead of having > the GC babysit them. Sigh.)
I don't know whether it's marketing or a broken but long-remembered promise, but garbage collectors always have the reputation of freeing the programmer of the responsibility of memory management. Managed languages have garbage collectors to prevent memory errors. Without making allocations from the managed heap subject to garbage collection, it would still be possible to write use-after-free bugs in most managed languages. --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
