3 ms·

ha YAML, when mentioned, always reminds that taking a look at the specs[1] is a great reminder that things can derail badly event without a large committee [1]

• draw_down 8y ago
  I knew someone in the comments would bitch about it being YAML. So write it in XML or whatever you want and transform it with a script. Jesus.
• modells 8y ago
  YAML has the odor of TLS when the winds are just right. Not to be tech religious, but over-engineered, complex, wordy requirements tend to be expensive to implement, secure, audit and support. Tome-like specifications like YAML, PDF and TLS are invitations to bugs and security vulnerabilities. I remember printing some 800+ pages of the early Adobe PDF spec from around 2002, it was a container format with multiple encodings, able to store JavaScript, JScript, executable code and more... and thinking “this is going to lead to no end of malware and most of these dangerous features will need to be disabled or removed.” JSON might not be the most expressive, flexible, precise or concise text data encoding, but it’s sure darn easy to parse with a solid, simple spec. HCL and TOML tend to be better choices for ease of mechanized configuration management.