That's a trade-off. Choosing "Do A but let the user change it to B in the Settings" is very similar to "Choose A", because nobody changes settings. You just move the debate to what the default should be. Not to mention that "Should we or shouldn't we have crap-tons of settings?" is its own trade-off.

> That's a trade-off. Choosing "Do A but let the user change it to B in the Settings" is very similar to "Choose A", because nobody changes settings. You just move the debate to what the default should be.

Okay, smart-ass, what's your solution? Maybe we should put the GUI inside a box with the "A or B" decision delegated to a mechanism that monitors a radioactive source. We'll call it Schrodinger's GUI.

I wasn't being a smart-ass at all. I said "you have to balance trade-offs", you said "no, you don't have to, here's a non-trade-off solution", and I said "no, you've just changed the trade-off". Many people seem to think that moving things into configuration is a "free" solution, and I am very non-sarcastically saying that no, it is not. My solution is to be aware that there is no "solution", and you have to balance trade-offs (which is what I said to start!).