3 ms·
Following this argument to its logical conclusion, why bother having any kind of standardized format at all, ini or otherwise? The program's config reader knows
by naasking 3y ago
Following this argument to its logical conclusion, why bother having any kind of standardized format at all, ini or otherwise? The program's config reader knows what it wants to read, why bother standardizing names, notation, section delimiters, or anything else?
- kybernetikos 3y agoI presume the argument the author of this article would make is because it helps the human writer of the file.
- naasking 3y agoAnd a standardized format takes that even further, since now text editors can be aware of more of the file structure and assist with highlighting, completion and more.
- kybernetikos 3y agoNestedText was mentioned earlier in this thread, and it takes the philosophy to it's logical conclusion. That conclusion includes schemas https://nestedtext.org/en/latest/schemas.html https://nestedtext.org/en/latest/schemas.html. Text editors could absolutely be written to understand schemas and provide the help you suggest.
- marcosdumay 3y ago> why bother having any kind of standardized format at all, ini or otherwise? So you can reuse the parsing code and the file-editing instructions. Standardization is not about catching errors.