Hacker News new | past | comments | ask | show | jobs | submit login

YAML in devop is essentially being used as a declarative language. They do have their place in domain specific applications, and can often be quite powerful.

While being able to write in any language gives you flexibility, I do wonder about maintainability down the line. How would this be addressed? Or it doesn't matter as this sort of code tends to be thrown away?




The issue with YAML is that the abstraction ceiling is way too low for its use cases. How do you maintain a 500 line YAML file? You have no tools to simplify it apart from super basic replacements

Meanwhile if I give you a 500 line python function you have a lot of tools at your disposal to refactor to improve maintainability (you could actually write basic tests for your CI pipeline config instead of having failures when the config gets pushed out)




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: