SledgeHammer01 wrote:
Much better design.
Nonsense.
SledgeHammer01 wrote:
so I usually provide an easy to use GUI for them
Which means you must STILL provide documentation. And a GUI. So now you have increased the work and time to deliver.
SledgeHammer01 wrote:
I know where you're going next... web.configs, web services, etc. don't have GUIs
So you create a GUI, and documentation for the GUI that handles multiple versions for a process that Operations/Support only uses once per install. Thus quite a bit of additional time and cost - which is your rationalization for ignoring the fact that it rewrites the file?
SledgeHammer01 wrote:
Entirely incorrect.
Something new for you to learn... http://www.w3schools.com/schema/el_sequence.asp[^] See the first example which says "which must contain the following five elements in order"
SledgeHammer01 wrote:
which has some awesome performance optimization,
Yes the high volume tps servers that I have been delivering for the past 15 years do have measured and proven production performance abilities.
SledgeHammer01 wrote:
The proper way to do ordering in an XML file is by using a key.
The proper way is to understand more about what "XML" means.
SledgeHammer01 wrote:
What does this have to do with anything?
What it has to do with is documentation. Please read what I said. Trivial applications might have config values that are understood without documentation but more complex apps require substantial documentation so someone besides the original developer has any chance of understanding what the values mean, how they should be set, what the relationship between different values, etc.
SledgeHammer01 wrote:
...and having a non standard API, but thats just me.
Yes it is you, because I didn't say anything like that.