Look at the path “configuration defaults” have taken. Whenever software has settings or can do things multiple ways, there is usually a default out-of-the-box setting.
Long time ago, the default was often whatever was easiest to program or took up the fewest compute resources: the variable is zero initialized by the OS, so therefore the setting will default to off.
Then, the rule became: the default should be the way most users will want to use the software.
Now, it’s: the default should be whatever causes the user to take the action that the developer wants them to take.
We are also seeing software with fewer and fewer settings. Developers are simply taking away the option and forcing users to do it the way the developer wants. This trend is aided and abetted by the current crop of ‘minimalist’ UI designers who insist that settings are bad and nothing should be user configurable.
Long time ago, the default was often whatever was easiest to program or took up the fewest compute resources: the variable is zero initialized by the OS, so therefore the setting will default to off.
Then, the rule became: the default should be the way most users will want to use the software.
Now, it’s: the default should be whatever causes the user to take the action that the developer wants them to take.
We are also seeing software with fewer and fewer settings. Developers are simply taking away the option and forcing users to do it the way the developer wants. This trend is aided and abetted by the current crop of ‘minimalist’ UI designers who insist that settings are bad and nothing should be user configurable.