Yeah, I like this approach. There's something about YAML that just sucks the joy out of programming. It seems like a giant step backwards when we have plenty o

Yeah, I like this approach. There's something about YAML that just sucks the joy out of programming. It seems like a giant step backwards when we have plenty of amazing programming languages in existence. Even when infrastructure yaml like cloudformation are wrapped by some SDK, it can still be a pain because you end up with stuff like... do_something("___((!-prickly_config_string_::might as well use yaml _blah-blah:blah))") Back in the days of java and xml, there used to be a distant promise of "binding" the xml to code (remember jaxb?) so that you could then just manipulate it fluently as code and then "marshall" it out back to xml when you were done. Those days and that promise are gone, right?