|
![](/i/fill.gif) |
Invisible wrote:
> Unix software, on the other hand, seems to regard giant text files (all
> with a completely different format) as the *primary* means of
> configuration, and a GUI as secondary to that.
That's because Unix doesn't have a registry. Hence, every program implements
its own configurations subsystem, and hence it's difficult to write a GUI
that understands the configuration subsystem of every program. If you do,
it's difficult to continue to update it in step with releases of the program
that break the syntax of the configuration files or add new options that
people want to use.
> Windows software tends to regard the GUI as the primary way to
> configure. And if there isn't a button for it, it's probably just not
> editable at all.
Not quite true. It's just not supported if there's no button. There's all
kinds of things you can tweak but only if you know what you're doing.
--
Darren New, San Diego CA, USA (PST)
Is God willing to prevent naglams, but unable?
Then he is not omnipotent.
Is he able, but not willing, to prevent naglams?
Then he is malevolent.
Post a reply to this message
|
![](/i/fill.gif) |