I've stated this position previously, but I'm a big fan of flexibility and configurability (up to a point).
We all use plenty of apps that expose a basic level of Settings that suits the majority of users and/or majority of needs, and then have an "Advanced Settings" section where the stuff the developer doesn't want you messing with unless you know what you're doing (subjective of course š ) are tucked away.
The other method I've seen work well is in Cakewalk Sonar DAW where there is a 'Show Advanced Settings' toggle which exposes a lot more options on every section of the Settings pages. This way, all those advanced settings are still found in the relevant Settings sub-menu (as opposed to a global Advanced Settings where everything Adnaved is hidden away together).
The good apps also have a 'Reset to Defaults' button/option so that when you encounter strange behaviour or issues, that is one of the first things that can be done - reset all those Advanced Settings to default.
I worked in the Software industry for over 20 years and you learn pretty quickly that (and this is not meant to be rude so please take the quote at face value) "you can't build idiot-proof software as they'll only build better idiots" and of course the other old fave "with great power comes great responsibility" š
So these things are always a balance. Configurability vs Complexity. Choice vs Locked down defaults.
And there's no perfect answer as we all sit on a spectrum of what we deem acceptable or desirable on these decisions.
As users - we might generally nudge towards more configurability as it gives us what we want.
As developers - we might want less configurability as that will reduce support volumes, simplify documentation, allow users to get productive quicker, etc.
Personally, I'm more biased towards wanting more choice, but also accepting the responsibility that comes with that. I.e. with more complexity I need to commit to reading the documentation, I might need to ask questions in community forums, I might ned to invest more time trying different things, etc.
There's an implied agreement between developer and user - by giving you all this cool stuff that they have invested so much time and effort into (and that includes in-app help, documentation, tutorial videos, etc.) you will invest a portion of your time learning how to use it by consuming these resources. The reality is that most tend to just dive head-long into it. While some will revert to researching first, others just hit the keyboards and rant away in forums. In short, they take no personal responsibility and breach the implied agreement with the developer through self-entitlement/selfishness explained away as being too busy, bad software design, etc.
OK, putting the soap box away now š