I will have to balk on Linus' opinion in this situation. I will admit that for a hacker, environment variables are the way to go. Quick and easy ... enough said on that. *If* a system is going to be more user friendly, then configuration files (text based) are the way to go. My reasoning for this is that it is really easy to have the documentation right there in the config file. Don't get me wrong - I don't believe in rewarding stupidity - if you can't read the documentation you get what you deserve. I do enjoy the ability to pop into a config file, seeing potential options and tweaks I can do and selecting them appropriate options based on that. A GUI tool that could easily edit this file should be the ultimate goal (or maybe this should be left up to the appropriate desktop environment *vendors*).
On Tue, 3 Dec 2002, magenta wrote: > On Tue, Dec 03, 2002 at 11:29:34AM -0800, Linus Torvalds wrote: > > ... They are also often much more efficient and > > easier to use than config files (ie "just say no to another config file > > parser"). > > Another note: The amount of code needed to parse a configuration file isn't > signifigantly more than the amount of code needed to check the various > environment variables. > > -- //========================================================\\ || D. Hageman <[EMAIL PROTECTED]> || \\========================================================// ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
