Developers continue to debate the question of memory management solutions. Which is best? Although Objective-C’s retain/release runs smoother and faster than Java’s garbage collection, it places a much larger burden on the developer and introduces a much larger risk of memory leaks.In the first of a series of articles that detail the important differences between Java and Objective-C, Marcus Zarra compares and contrasts memory management in Java and Cocoa/Objective-C.
Maven is an incredibly powerful tool that allows for the easy maintainability of Java projects. But what if your project is more complex than a simple Hello World applet? Marcus Zarra introduces the Maven multiproject concept, which is designed to facilitate the management of complex projects.
Well, while you *can* make mistakes in ObjC and leak memory, it’s just as easy to leak a non-memory resource (file handle, window) in Java.
If you follow a single rule it’s easy to get memory working all fine in ObjC: everything that you either create (alloc), or copy, or retain has to be released; everything else not.
The only thing to avoid are cycles, but hey, how often do you really want to create cycles in your application?