2 ms·
I feel like using the incomprehensibly error-prone and inscrutable sudoers format as an example kinda argues against your point. (I do agree that JSON is a ter
by kelnos 2y ago
I feel like using the incomprehensibly error-prone and inscrutable sudoers format as an example kinda argues against your point.
(I do agree that JSON is a terrible configuration file format, though.)
- amiga386 2y agoMy argument was not that sudoers is good - it's crazy overcomplicated. My argument was data interchange format standards are orthogonal to config files. They don't have the same goals. A programmer who thinks "I'll use JSON|YAML|TOML for my config file" - well, you didn't solve your first problem (what should the config look like, in a way that makes sense and is easily readable, understandable, updateable by the user) and you added a second problem before you even started solving the first - whatever your config looks like, it now also has to be 100% compliant with some data interchange format and support all its features, and that's going to require a lot of code - and then we get into whether you write the compliant parser/generator, or if someone else does and you do/don't audit every line of it. And then on top of that you add an additional pile of code to parse/generate whatever your actual config format is.