there are two kinds of "human editable" to consider, that these people making these standards do no make clear.
1. a human can find particular strings or numbers and change them, in a file already built by some program. they might be able to use the sed program if the strings are unique.
2. a human can create this file from scratch ... at least when the needed size is not too large.
i prefer a format that works for both needs. JSON and XML do poorly at number 2 (BTDT). so i went with python as the format for my things. most of my configs are fairly small.
1. a human can find particular strings or numbers and change them, in a file already built by some program. they might be able to use the sed program if the strings are unique.
2. a human can create this file from scratch ... at least when the needed size is not too large.
i prefer a format that works for both needs. JSON and XML do poorly at number 2 (BTDT). so i went with python as the format for my things. most of my configs are fairly small.
dir = "~/keep"
blocksize = 4096 # for both read and write error_action = retry retry_times = 15i think that with a few examples, most computer users that can edit a text file can make these. on the second example, some names like "retry" and "abort" could be predefined in the dictionary used as the local namespace when calling exec().
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.