> This is the central problem with all programming today. Sweeping generalizations rarely age well. > You can think of everything as configuration. Parameters

> This is the central problem with all programming today. Sweeping generalizations rarely age well. > You can think of everything as configuration. Parameters of a function are just configuration for that function. No, parameters of a function are contextual collaborators which participate in a function implementation. Configuration canonically influences a program aside from its individual run-time interactions. Is a value given to the cosine function a configuration? Words matter. > Every task in software is wanting to change what is displayed in a user interface of some sort. This is a myopic perspective. Software processes data into information which provides value in context. This may never be "displayed in a user interface." To wit, the network gear involved in my posting this reply most certainly qualifies as a "task in software." So, too, is the software running in the power companies involved. It would be quite a stretch to categorize them as "wanting to change what is displayed in a user interface."