What are your thoughts on ini? My perspective is that >9/10 toml's are just ini files, straight up. The nesting seems rare, and rarely confusing to me.
I obviously disagree about the ease of json editing. jq tells me errors, sure. But formats where we don't need bespoke tooling, where notepad.exe work fine, are I think probably what config files should be more like.
My only experience with toml is complicated nested ones because I'm sure that the maintainers outgrew whatever was simple. Off the top my head it's just containerd config. Yaml probably a better choice than json and ini is fine if it gets the job done, but it's it really more than .env? My opinion is the env should do a lot of lifting anyway. I'm thinking there's always "tooling." My toml might syntax but be logically incorrect all the formats have that problem and linting doesn't stop at json. Like changing my containerd config I don't really know if it took or not
Comments
What are your thoughts on ini? My perspective is that >9/10 toml's are just ini files, straight up. The nesting seems rare, and rarely confusing to me.
I obviously disagree about the ease of json editing. jq tells me errors, sure. But formats where we don't need bespoke tooling, where notepad.exe work fine, are I think probably what config files should be more like.
My only experience with toml is complicated nested ones because I'm sure that the maintainers outgrew whatever was simple. Off the top my head it's just containerd config. Yaml probably a better choice than json and ini is fine if it gets the job done, but it's it really more than .env? My opinion is the env should do a lot of lifting anyway. I'm thinking there's always "tooling." My toml might syntax but be logically incorrect all the formats have that problem and linting doesn't stop at json. Like changing my containerd config I don't really know if it took or not