this post was submitted on 03 Jan 2025
101 points (95.5% liked)
Programming
19689 readers
356 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You shouldn’t write complex yaml files. Keep it simple and yaml is great. Do complex stuff and you’ll hate your life.
If you write your own tooling then it's great. The vast majority of us are using other people's tooling and have to deal with their imposed complexity. I for one hate GitHub actions with a passion.
None of the complexity of GitHub actions would be solved with any other configuration language. It needs to be a full scripting language at minimum. The problems with GHA have nothing to do with yaml.
I'm convinced everybody who told me that "GitHub actions are great!" were just part of one big prank.
I have the same feeling about kubernetes.
Kubernetes seems closer to the top of the tower of Babel than to the basement. Part of it anyway.
I wouldn't call those examples complex
I think that proves the author's point. I also think you're right in regards to the comment you replied to.
The description of the post said “complex yaml files”.
If you keep it simple, then probably JSON is easier. In other cases too.
JSON is not easier for most strings. Anything multiline for example.
But yaml is a superset of JSON so you literally can use JSON and it’s still valid YAML.