FUN W/ BOB

Aperture vs iPhoto for jpeg file management

So even though I’ve gone back to shooting jpeg with a P&S camera, I’m still currently using Aperture to manage my photo library instead of iPhoto. Why is that? Well despite the fact that iPhoto is maybe a tad easier to use and quicker to navigate, there’s at least two things that are keeping me using Aperture instead.


First is its keyword structure. In iPhoto, each keyword is its own keyword and its own keyword only, whereas with Aperture, there’s a Hierarchy. So for illustration, say you have a Keyword called
Redwoods. Redwoods are trees of course, and suppose you also have Trees as a keyword. So you put Redwoods under Trees, but Trees is already under Nature, which is itself under Outdoors. What this means is, when you apply the Keyword Redwoods to that shot you got of The General Sherman during your Summer vacation, that photo automatically inherits all the keywords above Redwoods. Make sense? See, this way when you go and search for Outdoors (or Nature or Trees for that matter), the shot of that magnificent General Sherman will pop up, even though you didn’t apply that keyword directly to that photo; since it was a Parent in the hierarchy of the keyword you did use (Redwoods), it’s applied automatically, or assumed.

Second, is the fact that I still do tend to tweak my photos. Yeah it’s not as much as when I was shooting RAW, but since this camera shoots a little more “full-frame,” instead of a more widescreen format, I find I like to spend some time cropping some pics here & there to add a little more ambiance to them. In iPhoto, when you edit a picture, the program keeps the original, but then creates a copy of the picture with the edits you made. This means, if you change the brightness of a picture, now you have two almost identical files, with two almost identical File Sizes, essentially doubling its drain on your Hard Drive space (if the original was 2MB, you make an edit and now you are taking up 4MB for the edited & original files).

Aperture doesn’t do this, it instead displays onscreen what the commands you input for edits will produce. In this way, the original file is kept, but no ‘duplicate’ is made, rather just the instructions for creating it, which take up far, far less room (orders of magnitude less).

So yes, iPhoto is more friendly by a smidgeon than Aperture (especially 1.5, the original version that I own), but it would also lead me to expanded disk usage, and I’d also have to be much more Johnny-on-the-spot with my keywording. Hey, maybe the next iteration of iPhoto will inherit the “non-destructive” editing of Aperture and the keyword hierarchy too, but until then I think I’ll be sticking with Aperture.

Peace.