@toiletpaper @lanodan @NonPlayableClown Allegedly perfect, browser says it is rendering in standards-compliance mode, probably something I did but I don't wanna debug text formatting. I am gonna pipe the shit through "fmt -l72" and wrap it in a <pre> tag. > That's an endemic problem with sw dev. "Penny-wise but pound-foolish" except for overspecifying the pennies to such an extent that nobody can get the pennies correct. Many such cases. > but because it's human readable. This is the line everyone uses. This is not my experience. If 95% of the YAML spec were removed, it would be human-readable. It is, at least in theory, but in practice it has a lot of punctuation and ambiguity when reading. I hate JavaScript and I remember when YAML was what we used because the alternative to YAML was XML and I still prefer JSON. Human factors aside, I mean, generating it makes a feller think "If I made a plain-text data format and I tried to make it Perl, how close would I get to this?" I mean, off the top of my head: --- asdf: - "This is how people think YAML is going to be." - "This much would be fine." :jkl: - "What the fuck was that extra colon?" - "What does it mean if there's a colon at the *beginning*, too?" - Under what circumstances are bare strings allowed again? okay: wait: "What can you use for keys in associative arrays?" :wait: "Do these keys collide? It depends on if your language has interned symbols and whether or not it makes you deal with YAML as a massive parsetree." fuckin: - - "What?" - "What does that mean?" - baffling: ["Okay, hold on.", "Lemme find the YAML spec.", "Does that even parse?"] - "Yes, it all parses." - "I checked! (I didn't read the spec, I just pasted it.)"