06 Feb 13. While the philosophy of the two biggest operating systems for personal computers seems to be having programs that do everything, the better OS, Linux, a variant of Unix if you will, has the philosophy like its bigger brother that it is better to have many small programs that do just one thing perfectly and chain output between them to get the best, and in the process, fastest performance possible. Along that philosophy I have been playing with a new (to me) printing program that does basically just that, prepare images for print. Now that may seem odd as I print so very little, but one can print to file as well as paper, and the results I'm seeing are very encouraging. Its only drawback so far that I can ascertain is that there is a rather steep learning curve, but one which is offset by the best support I've ever encountered, period. So I've been spending some time lately working with this program to see if I can get more out of a huge backlog of images (c70K) I haven't shared yet. My efforts to date, and I'm just beginning to understand the program, strongly suggest that it is going to be the ticket. The part I haven't yet fully determined is exactly where it will fit in the post processing workflow. At the moment I believe that it will be either used after I've made all the manipulations to the image I want, or, it will be used by itself with out any prior manipulation to the images. I've worked with it both ways and found that each approach has it own rewards. Today's submission was worked entirely in the print program without anything additional being done to it. In other words, the original RAW file was loaded into the program, a few small "corrections" applied, and then it was printed to file as a .jpg. So here is a shot from the '07 trip to the Grand Tetons. You make your own evaluation, but I like it. D200; 18 - 200; Aperture Priority; ISO 100; 1/160 sec @ f 13.