helm is a bad solution to a lazy thought out problem. why would i template yaml from another yaml and without versioning and weird if else constructs just for d

helm is a bad solution to a lazy thought out problem. why would i template yaml from another yaml and without versioning and weird if else constructs just for deploying which clearly should be json? because we devops are obviously not able to abstract the problem. oh you switched from nginx to haproxy, lets change all the labels in my git comitted repos where my yaml lies. oh the author changed the way the helm chart works, lets do manual compare to see what changed. Oh k8s changed the api version again, lets change all the yaml. and helmfile on top of helm -> more abstraction in the wrong direction -> love it. i would much rather use something like starlark and program my deployment needs against the correct library version of the k8s api which my cluster has and get the final yaml for free instead of templating and forking and maintaining dead weight every damn version.