Because whitespace sensitivity makes it very easy to make a whole bunch of annoying mistakes when shuffling code around, or copying it from one source to another (from text in one application to the editor in your ide for example). I find it supremely unpleasant to work with. Looking kinda a little bit slightly messed up should not be a critical syntax error that breaks the whole code.
I agree. I think ansible is great in principle, but the documentation is severely lacking. Like it’ll tell you to set a value, but not whether it’s supposed to be in yaml, environment, or something else. And if it’s in yaml, it doesn’t tell you the required context to make it valid. But when someone has taken all the documentation, all the tutorials, the articles, the example code, working code, and stack overflow answers and put them all into a blender, often a useful answer comes out.
Ok, yaml is fair game for a LLM. Whitespace sensitive language should die in a fire, markup or otherwise.
Why do you say that?
Because whitespace sensitivity makes it very easy to make a whole bunch of annoying mistakes when shuffling code around, or copying it from one source to another (from text in one application to the editor in your ide for example). I find it supremely unpleasant to work with. Looking kinda a little bit slightly messed up should not be a critical syntax error that breaks the whole code.
I agree. I think ansible is great in principle, but the documentation is severely lacking. Like it’ll tell you to set a value, but not whether it’s supposed to be in yaml, environment, or something else. And if it’s in yaml, it doesn’t tell you the required context to make it valid. But when someone has taken all the documentation, all the tutorials, the articles, the example code, working code, and stack overflow answers and put them all into a blender, often a useful answer comes out.