On Apr 4, 2007, at 2:11 PM, David Cantrell wrote:
So the correct solution is for the application to have an option
for how to store config information. The value of that option is,
obviously, best stored by it editing its own executable.
Or to create a directory just for itself in the root, because at
least that would piss you *both* off.
The correct solution is for the stupid operating system to realize
that every stupid application stores defaults and shouldn't have to
even think about this problem. We're talking about a trivial api,
even if we're dealing with opaque data -- the stupid OS should
decide, and the apps should write to that API. Even my own code
doesn't decide things like this -- I write an API that handles
picking file paths and opening file handles, and then all of my code
uses that API. Boom. Done. I never think about paths again.
I thought the whole point of an operating system was that it came
with libraries so that people didn't have to do work unrelated to
their specific application. Choosing where configurations are stored
is pretty unrelated to what most of my applications do, and they
should definitely be outsourcing it to the OS.
And I also hate mailing lists that don't default to replying to the
list. Sorry David. :/
--
Charm is a way of getting the answer yes without asking a clear
question. -- Albert Camus
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
