@zack_overflow I am going to segfault a config file 1st thing tomorrow. Will gdb detect it??
@zack_overflow The most cursed of the markup languages
@zack_overflow We need to shut yaml down until we can figure out what the hell is going on.
@zack_overflow For reasons I cannot explain, the developer who uses a feature like this is always the developer you would least want to use a feature like this.
@zack_overflow This is so much less cursed than "yes" being parsed as true and "no" as false...
@zack_overflow I did not need to know that and hopefully I will never encounter that in production
@zack_overflow This feature has been used in every database.yaml in every rails project for the last 10 years.
@zack_overflow Anchors, super useful, can make yaml somewhat bearable...
@zack_overflow Wake up babe new way to segfault just dropped
@zack_overflow Yeah, anchors are nice. Using it for k8s setup to avoid re-defining common parts like runtime or something else. Although, if you create yaml programmatically, may take some time to make it work properly (escaping)
@zack_overflow YAML supports random things with random syntax and will break random stuff in random ways in the future (guessing from history: it broke random things in the past for the fun of it). It's a disease, not a format.
@zack_overflow thanks i would have been very happy not knowing this
@zack_overflow These made our CircleCI pipelines much more maintenable
@zack_overflow yaml supports lots of weird things! you can have a map as a key of another map! you can have array as a key! you can have a map as a key in a map, and in that map have another map, and go many maps deep! you can also have a map with an order!
@zack_overflow On your path to become a YAML engineer
@zack_overflow I feel compelled to link it... noyaml.com
@zack_overflow GitHub Actions's YAML parser doesn't do references and anchors, though, alas.
@zack_overflow Which makes it a graph as opposed to multi tree format of many other formats.
@zack_overflow Yet another reason to not support YAML.
@zack_overflow Last time I used there were parsers that did not support it.