Re: What is the rationale behind keeping preferences in one place and "Application Support" files in another?
Re: What is the rationale behind keeping preferences in one place and "Application Support" files in another?
- Subject: Re: What is the rationale behind keeping preferences in one place and "Application Support" files in another?
- From: John Stiles <email@hidden>
- Date: Thu, 8 Dec 2005 10:49:24 -0800
On Dec 8, 2005, at 10:45 AM, Andy Armstrong wrote:
On 8 Dec 2005, at 18:37, John Stiles wrote:
I know - that's what I'm objecting to :)
What?
Putting prefs beyond the reach of defaults based on the (IMO)
arrogant assumption that users aren't competent to use it.
As an example: I was recently able to help a technophobic user to
configure his system by sending him a shell script containing a
series of defaults commands. Not only that but when I explained to
him what it did he was delighted by the possibilities afforded by
the command line.
Disabling the use of a tool because we /think/ users won't be able
to benefit from it is arrogance.
Jeez! When did I say that I wanted to put things "beyond the reach of
'defaults'"?!
I'm saying that in the 99% case, it's irrelevant. I didn't say
"nobody should ever use defaults" or "we should get rid of defaults"
or anything of the sort. There's a 1% case where defaults is super
useful... I agree wholeheartedly. If you use defaults and think it's
the best thing since sliced bread, that's cool. Nobody is planning on
taking that away from you. Certainly it's outside of my reach ;)
There are a lot of great reasons to use NSUserDefaults. I posted them
earlier. IMHO, some of these are cooler reasons than the defaults
command line tool. That's ALL I'm trying to say.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden