4 ms·
I use .ini. I have tried everything. I always return to .ini as the easiest way to express static data regardless of complexity.
by tqwhite 3y ago
I use .ini. I have tried everything. I always return to .ini as the easiest way to express static data regardless of complexity.
- crabbone 3y agoTry configuring systemd (that's including all the services it has to run) in INI... I mean, it's sort of what it does with unit files... but this means you now have hundreds of INI files. They are all related, but you don't really know how. You could try versioning them, but you don't even know where all of them are, so every configuration change is a minefield. Or, another, perhaps a simpler mental experiment: try writing a CloudFormation template in an INI format. After all CloudFormation templates are configuration for the service that creates virtual appliances. If you look at the current JSON / YAML way to define this kind of template, you'll see that YAML isn't expressive enough to do it, and they had to invent a lot of meta-language conventions to be able to express what they need. With INI your struggle will be monumental to accomplish that.