It has been a month now, since the Product Manager Aperture from Apple notified me, that they had been able to reproduce the problem I discovered with Aperture 3.0.3. For those who do not remember it, you can find it here: Trouble with Aperture 3.
Big Guy
But yet there is no news on any solution by Apple. Apple is known to build high quality hardware, which in turn is quite expensive. I do know plenty of creative professionals use Apple hardware and software for their daily living. But for the hardware it seems it is worth the money. Apple claiming Aperture to be the a piece of software for professional photographers, I would have expected them to put in a bit more effort in making the software usable. After all, we spend money in this as well.
Hungry Guy
Working in a large company using allot of specialized software, either bought or build in house, I do know the problems a commercial software company might run into. I met plenty of so called specialists delivering software, what I would rather call stirred bullshit than a ready to market piece of software. No concept for the usability, and if you scratch below the user interface, all you see is failures and brainless code. When ripping apart the code they had delivered and telling them, that whatever team member delivering this quality of code to me would be whipped until he would have fixed it, the only question the Product Manager would ask was:
How do you come to thinking, that we would accept your review, unless you found anything positive in our coding.
But there had been not a bit of positive in their code. No documentation, no brain, no nothing.
Lazy Guy
On the other hand I had to deal with companies, whose developer at first did not believe in their code being wrong. Having a black box without having the code, I had to analyze the behavior and guess from that. But as soon as I told them where to look for the bug and could deliver them a piece of code reproducing the same error they had, it had only been a matter of days until I got the version including debugging code a I demanded and a few more days until I got the final fix.
Big Guy II
Of course, since the companies I have been working for are bigger and in need for far more reliable software – either by life and on the other side a huge amount of money depending on it, you do the math which one is more important – the kind of pressure one can build up against the software company differs to the one a single photographer could build up against Apple.
Cute Guy
But still, I do get pressure put upon me by my model requesting me to deliver the promised shots to her. As of that, I had to have my Aperture 3.0.3 running all night, just to export 15 shots. And from my point of view, since Aperture is a black box to me, as I do not have any insights into the code, it seems like Apple does have a huge problem with its memory access within the export. Numerous threads are created and blocking each other by locking its memory.
Sleepy Guy
Maybe its really time to dig into Lightroom by Adobe. Its user interface is a mess, compared to Aperture. But this is one thing I might look over, when performance underneath is matching my requirements. Or maybe one should ask Steve Jobs in person, but him being a business person, he’d rather spend his time in a gadget like the iPad instead of a piece of software that does not bring in a percentage of money compared to the iPad.
Recent Comments