I don’t know about you, dear, but probably non-existent reader, but I thoroughly enjoy it when things don’t work properly. Nothing annoys me more, for instance, than entering my car, turning the key in the ignition, and the engine starting. Getting to my destination on time, and in a safe and comfortable manner is one of the biggest irritations I can imagine. As you can guess, Photoshop CS4, was, there4, an almost constant source of perfect annoyance. I didn’t enjoy the way it rarely, if ever, crashed. I hated the fact that it seemed to understand how much memory my computer had, and did its best to operate within those tolerances. You can imagine, then, the upgrade to CS5 coming as a welcome relief.
Finally! The heady mixture of cannibalised memory and slow as mollasus-mixed-with-dogshit performance, regardless of your system specs, and those sublime moments where you’d accidentally nudge a layer 1 pixel and have to wait for a couple of minutes as the swapfile seemingly crushed itself to a singularity under the awesome reckoning of Adobe’s frivolous and lazy coders. My God, I love CS5.
Even as I use it now, it’s making me smile. I just had a single file open, and granted, it had many layers, and it was a 16 bit image, so it took its time to save. During these saves, it actually sounds like there is someone inside the chassis of my computer sawing large chucks of wood. It is, of course, just my hard drive struggling to cope with photoshop’s galactic processing requirements. Whilst none of that is unexpected for the larger files a photographer has to work with, it doesn’t explain why, directly after saving that file, I also saved a much smaller file, containing only a single layer and a contrast adjustment, which took twice as long to save and also denied me access to to any other programs; my computer had frozen solid with the kind of stricken helpless fear once reserved only for youngest catholic boys in the remotest Irish diocese.
So as you can see, the brilliance of CS5 is that it’s always keeping me on my toes. Never getting predictable like, say, things that work how they’re supposed to? It’s always there, smashing into things, causing a nuisance, freezing my computer, having to be restarted every few hours because it refuses to release precious stockpiled memory like the rotund children in sweetshops of yore, forced, by well-meaning parents to release the handfuls of cola bottles from fleshy fingers webbed by saliva and sugar. Portly little buggers.
Anyway, after two years of this shit, in comes Adobe Photoshop 6: Bigger. Stronger. Faster. Just not at any of the stuff that made CS5 so infuriating to work with.
A quick rundown on what it offers,
Slightly faster liquifiy tool.
A bunch of shit I’ll never use.
A bunch of stuff for hobbyist photographers to completely wreck their photos.
Slightly different UI that does nothing to enhance usability, but rather just makes things slightly confusing as you initially get used to it.
Background Save function that no longer freezes the program while it saves, but instead intrusively freezes the program during random intervals, lasting 30 seconds at a time, mostly when you least expect it.
Recovery feature (See above)
Couple of extra blur filters. Amazing!
So if you usually use Photoshop for retouching purposes, this upgrade is far from a no-brainer. 40 days of use and I’ve gone back to CS5. Why? Because whilst using CS5 is the equivalent of standing in your Sunday best below a giant wobbly mountain of crap, you can do it with up to 50% less memory than Photoshop CS6. From a cold start, on my iMac, CS5 requires 308mb of memory. CS6: 506mb. What if I only plan to use features that have been present in the Adobe suit since Photoshop 5 back in 1999? I have to give up a further 200mb of memory for the privilege of a dark UI?
Loading a TIFF I’m currently working on that’s so far sitting at about 1gb file size, CS5 uses a whopping 5597mb to load it (If I close the image, CS5 gives me back a generous 200mb of memory, deciding, for whatever reason, to continue holding onto the other 5gb it took to load the image). In cs6, though, 6500mb is required (It gives back an even more impressive 8mb when I close the image). So in order to load and work on the same image between versions, I’m expected to give up an extra 1gb of memory. For someone who doesn’t use a single new feature-what’s the point?
And thus we arrive at my point. Who are Adobe making these products for now? Not me. Every single addition I’ve seen in the last few years has been for a userbase that never existed. It adds feature upon feature that doesn’t really add anything to a photographer’s workflow. More and more features give them a reason to justify higher and higher software prices, but in the meantime, I’m still using the same basic tools I’ve been using since Photoshop 5. Not CS5, I’m talking 1999.
Maybe I’m completely wrong about everything here, but as someone who uses PS for up to and over eight hours a day, something just doesn’t feel right. What was once a beautifully coded, succinct tool for photo editing has now become a bloated mass of functions that serve almost no purpose for the audience this program was originally intended for. Adobe are heading the way of RealPlayer, and I’m stating categorically that as soon as a reliable alternative appears, I’ll be jumping ship. They lost my loyalty a long time ago.











Recent Comments