3 ms·
That's not really a problem with YAML it's an abuse of YAML. Accidental turing completeness is a problem all over, too. I remember using Ant 15 years ago - buil
by hitchstory 3y ago
That's not really a problem with YAML it's an abuse of YAML. Accidental turing completeness is a problem all over, too. I remember using Ant 15 years ago - built in XML. It was the same problem and that wasn't XML's
I think a lack of type safety is the main problem with YAML - a wrong indentation, a typo in a key, a string that gets parsed as a boolean, etc.
Other than that I think it's a great format - terse and far less syntactic noise than other formats. This is why I wrote https://github.com/crdoconnor/strictyaml https://github.com/crdoconnor/strictyaml so people could write type safe yaml and get instantaneous, clear error messages on those things.
- bradrn 3y agoThis reminds me of the Dhall configuration language: https://dhall-lang.org/ https://dhall-lang.org/
- verdverm 3y agoI think more of JSON5, but the opposite direction
- PH95VuimJjqBqy 3y ago> That's not really a problem with YAML it's an abuse of YAML. absolutely true, but the same happened to XML. XML is actually awesome with tooling that hasn't been matched to this day (XSD, XSLT, just to name a few). But people abused it, it got a bad rap, browsers made JSON preferable, etc. But the point is that companies are using YAML for these things and we're starting to see attitudes shift just like they did when the industry went nuts and abused XML.
- Aerbil313 3y agoNickel (https://nickel-lang.org/ https://nickel-lang.org/) is a new configuration language which builds upon lessons learnt from YAML, TOML, JSON, JSONNet, Nix and many others. It has optional types and logic (functions, variables) for when you need it.
- 8n4vidtmkvmk 3y agoEvery language website should have an example or 2 on the homepage. Show me the code/syntax, and add an explanation if you need to but stop with the feature lists. If it can't explain itself then... I don't know.