kaydell-leavitt asked: What do you think of garbage collection in Objective-C 2.0 for Mac (doesn't work for iOS)?
Well, I know that iOS is all ARC-based, but I have definitely noticed a lot of thigns where running in a non-memory starved situation that a lot of allocated memory tends to stick around indefinitely until you actually need it in another application. The only thing that gives me reliable information about what memory my application is using that is legit is the Instruments application from inside of XCode. Admittedly, I think that tool is simply fantastic, and an invaluable resource when doing any significant debugging.
As far as whether or not garbage collection does the number one GC complaint I have with a language like, say, Java, I have yet to see GC end up doing something like lock my application up to a point where I am unable to do meaningful processing or user/UI interaction. The only times I’ve seen that are when I end up pegging the CPU(s). A great example of this is the introduction to NSOperationQueue in the Big Nerd Ranch book (this book, incidentally, is fantastic and I highly recommend it as well as their iOS programming book), where loading a couple hundred images pegs even my massive Mac Pro desktop (the default version sets a max number of simultaneous operations ,but that is BORING! If you’re working through a book teaching you a programming language and you don’t change things up to try to learn a few more things, you’re doing it wrong!).
As far as comparing it to other versions of Objective C, I’m far too new to the language to gauge it well.