>YAML Configuration files
FUCK KUBERNETES
YAML Configuration files
declarative > imperative
you can also use json instead
Thats even worse
TOML are the most comfy. It's intuitive.
XML is the best for configuration. Prove me wrong
thats going to be an absolute yikes regards from me yikesfrogs
Not that poster but it is worse, json is not meant to be a configuration format, but zoomers like you shoehorn it into everything.
The only time it makes sense is when your json is very simple, but if your application grows it's such a PITA.
Named closing tags are shit. Symbol hell and a pain to type with all the & etc.
nginx style config is the best.
>json is not meant to be a configuration format
Its genera purpose, sure it wasn't meant to be written by humans
You’ve got something better?
Feel the hipster power.
YAML is a horrible markup language
I want to nakadashi sagiri
>nginx style config
It just looks like a reduced JSON, doesn't it?
.ini is love
.ini is life
[(You)]
based = True
redPilled = True
> conditionals
> loops
> variables hacked in via Jinja templating
They should've used a programming language, not hacked one in via yaml. Though I guess, since yaml is a superset of json, you could just use Dhall - though first-class support would be better
do you even AWS, OP?
>not encoding your config as set of declarative statements made up of s-exprs/prolog terms.
It ain’t even markup language, bro
yaml stands for yet another markup language but maybe I just took the bait
why would you use kubernetes in the first place lmfao
>whitespaces between "="
>t. retard
top-tier
#!/bin/sh
. ~/.program.conf
echo $foo
echo $bar
echo $baz
the contents of ~/.program.conf
foo=lorem
bar=ipsum
baz=dolor