Validating Kubernetes YAML for best practice and policies

Re:Validating Kubernetes YAML for best practice and policies by aliswe on Sunday August 09, 2020 @10:58AM (#24100010)

That's a map as a list element, iirc the terminology. But check out this.

When studying the Yaml spec I discovered that a map property (key: value) can have not only a string as its key, but any value. Even a list. (cue screams)

[ Parent | on HN ]

Re:Validating Kubernetes YAML for best practice and policies by shahsyed on Sunday August 09, 2020 @11:03AM (#24100034)

Here's another reason why YAML is bad:

the fact that I have to read the spec to figure out what's going on.

It should have been fairly simple to do this.

Why do I have to know the difference between ":" and "=" ...?

[ Parent | on HN ]

Re:Validating Kubernetes YAML for best practice and policies by Already__Taken on Sunday August 09, 2020 @11:58AM (#24100440)

Why didn't anyone learn from CSS when we all made pre-processors like stylus, less and sass that added white-space sensitivity. It's not great.

I thought HCL was one of the best attempts at a terse config language. Shortening foo { bar { bazz {} }} to foo bar baz{} cleans up plenty.

[ Parent | on HN ]