Options do become dangerous to the team building the UI, though. It's easier to add another option and the keep the previous behavior as default than to do the hard work of figuring out what the best behavior is and then, if the new behavior is better, having the courage to change the default. Having no options is good for discipline as it removes the temptation of doing it the easy way.
There's also the problem of bugs. Software with more settings have more code paths. It's harder to test, and harder to refactor.
There's also the problem of bugs. Software with more settings have more code paths. It's harder to test, and harder to refactor.