Article:  |
Cleaning iPhoto | |
| Subject: | That's honorable | |
| Date: | 2004-03-01 22:53:30 | |
| From: | brian_d_foy | |
|
Response to: That's honorable
|
||
| I can understand your disappointment, but I have a different perspective. I would like to control other applications with whichever tool I decide to use, whether that is AppleScript, Perl, or something else. I cannot expect the application designers to anticipate everything I might want to do. Indeed, I would rather have the iPhoto developers concentrate on getting rid of the file-based storage system they use on the backend. | ||
Showing messages 1 through 2 of 2.
-
RE
2004-03-02 13:47:37 r_miller [Reply | View]
Oh I understand that point. I do not think Apple should cripple a program so that advanced users cannot alter things to get what they want out of it. However, the ability to reduce image (size) and discard duplicates is in such demand it should have been included all along. That's all I was trying to say. Yeah, I am glad that Apple is leaving the backdoor open so developers can come up with new solutions. I just think Apple should do some of this on the front end. iPhoto I think is great, but its feature set is not much and now that we are paying for it, I expect more.
I hate to bring discord to this happy gathering, but I will.
I think this reply demonstrates why a lot of *nix users have taken so long to recognize mac as a resonable alternative to other operating systems. It was (pre os x) an operating system that was SO user-centric that the users gave up any responsibility for what they generate. And, on the flip side. If an advance system user would ask how anything complicated was done with a mac. They were likely to to be met with "well why would you want to" or "who would do something like that". As if the only things worth doing were things that you could associate with pretty pictures.
As polite as this user may be, he still sounds like a user stomping his feet, demanding the developer think of everything he could possibly imagine, give him an eloquent graphical way to do it, and do it yesterday.
The reason that Unix tools are generally command-line and compos-able is that every application wasn't designed to do everything (except maybe emacs:-), and the USER took responsibility for what he generated, provided he had some chain of tools he could pipe together to do it.