Paul Allen Newell
pnewell at cs.cmu.edu
Wed Jan 4 08:40:12 UTC 2012
On 1/4/2012 12:30 AM, Steve Searle wrote:
> The case against extensions in this context is that the user shouldn't
> have to change if the shell script is rewritten in a different language.
> Having to change from foobar.sh to foobar.pl just because of this change
> isn't user friendly. And what if you re-wrote it in C?
> But although you can make a case, it isn't an open and shut one, but a
> matter of preference I guess. And I certainly think .conf on a file is
> useful. And maybe even .d
As I have stated earlier, my take is that extensions should be a clue as
to what the file has but not something that should be "fixed" as in MS
More information about the users