Re: Mission creep
A glimpse of reality. This is how stuff happens. The first and maybe only version of the code is written for a single, constrained situation. My first FORTRAN program (the initial attraction was "You mean I don't have to do my own arithmetic any more?!") was to take readings from levelling (did you know there were surveyors staffs calibrated in decimal feet) and metric measurements from the Hiller borer and print out lists of numbers for me to draw stratigraphic sections by hand. Not too many people were going to want that one.
I admit to a certain amount of conflict over this one.
As a sometime scientist the computer was to be used as a tool like any other instrument such as a microscope. However you should know your tools, e.g. if you're a microscopist setting up the Kohler illumination should come naturally to you. If you're going to write programs to do a job you should take care over them.
OTOH a high level programming language should provide a high level abstraction of the platform and it might be reasonable to expect the provision of a view of directory contents consistent from platform to platform to be a part of that abstraction.