Personally I have embraced using sqlite as my configuration infrastructure, as the more I've used configuration formats, the more I've felt they are glorified databases.
Personally I have embraced using sqlite as my configuration infrastructure, as the more I've used configuration formats, the more I've felt they are glorified databases.
Glorified? They're just text files.
The reason they're called configuration files is because they're often meant to be edited directly by the user. Which is why there are so many configuration formats, since everyone has a different opinion on the ideal UI/UX.
You can store configuration in an actual database, but asking your users to use SQL to change it is sadistic. In that case you really need a UI to allow users to change configuration, which defeats the purpose of the simplicity of configuration files.
Yes, but in various ways in imo they require similarish purposes to databases.
Hence why I prefer something like sqlite.
Text config are good for wildcard configurations such as manifest or cargo.Toml.
But for a fixed and immutable configuration with multiple data types I think databases are better.
I think you are conflicting user needs with developer needs.
As a user, I would never want to edit a config on file using SQL!
A clear example of text as UI is git rebase: move around lines, rename words, press save and quit. It works great as a preview of the rebase.