11–20 of 88 posts
Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
For this, systemd syntax is a lot better than yaml IMO. In fact, I'd prefer if the tools you mentioned used something else besides yaml.
Unfortunately, there norway way that's going happen.
I heard you like abstract tools to do stuff, so I added an abstract tool to your tool to manage abstract tooling.
Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
also, fwiw, YAML is a data serialization format, not a configuration format. people who use YAML and pretend it's a config file format are either lazy, incompetent, or both.
Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
For this, systemd syntax is a lot better than yaml IMO. In fact, I'd prefer if the tools you mentioned used something else besides yaml.
To be fair, most of the popular DevOps tools can work with JSON instead of YAML just fine. And JSON can be easily generated from almost anywhere. I don't think you can work with systemd syntax as easily.
Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
Odd to call it "systemd syntax" when it predates the invention of systemd by a few decades: https://en.wikipedia.org/wiki/INI_file
Yes, it's inspired by INI files.
I heard you like abstract tools to do stuff, so I added an abstract tool to your tool to manage abstract tooling.
Earlier quoted context omitted.
For this, systemd syntax is a lot better than yaml IMO. In fact, I'd prefer if the tools you mentioned used something else besides yaml.
> In fact, I'd prefer if the tools you mentioned used something else besides yaml. To be fair, most of the popular DevOps tools can work with JSON instead of YAML just fine. And JSON can be easily generated from almost anywhere. I don't think you can work with systemd syntax as easily.
Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
RedHat basically sponsored the development of Systemd (among other things) so their full-throated support isn't surprising also, fwiw, YAML is a data serialization format, not a configuration format. people who use YAML and pretend it's a config file format are either lazy, incompetent, or both.
Odd choice using systemd syntax willingly when all other industry tools use YAML, IMO
RedHat basically sponsored the development of Systemd (among other things) so their full-throated support isn't surprising also, fwiw, YAML is a data serialization format, not a configuration format. people who use YAML and pretend it's a config file format are either lazy, incompetent, or both.