You can check into git so you have a history of changes?
So you can copy the config to another machine?
There are lots of reasons why text files are the preferred format to store configuration in.
Other than perhaps a slight performance boost, why do we want settings in a non-human readable database?
Hell, even Microsoft are starting to use json config files for stuff like Windows terminal because they know people like to be able to quickly copy and edit settings.
You are talking about the configs being stored in text files. The comment you are responding to was talking about being forced to edit text files to configure.
Yours is about the format of data representation and theirs is about UX.
The first step of not forcing users to edit text files is having sensible well thought out defaults. If I have to think about configs the designers of the app failed me.
The second way to not force the users to edit text files is by having a well thought out gui for the kind of changes you might want.
The format of how the config settings are stored is almost orthogonal to this questions. And yes, you are right, a text based format is preferable over a properitary binary one.