8 ms·
It’s because ppl are not using it correctly, it was designed for configs and now it’s being used as a programming language… a language without types and debugge
by coder-pm 20d ago
It’s because ppl are not using it correctly, it was designed for configs and now it’s being used as a programming language… a language without types and debugger. It’s frustrating devs because they find the issue at the deployment time, not the compile time.
Personally I did never pick the YAML as a first format for the configs, only my ruby friends did that.
- kelnos 20d agoIt's also terrible for configs, for many of the reasons specified in the article.
- coder-pm 20d agoFair point, that’s why I said I won’t pick it. But it still might be a good and simple choice for small configs, hand written. It does explode when it’s machine generated or templated. I think it’s also strictly connected with the ecosystem devs are working with, ruby or python devs usually pick YAML, JavaScript/Node devs with JSON - this is how it works, ppl chose what they know and what they are used to.