Do we have clj-yaml fatigue? Of course we do! But I think as stewards of this lib, we should address: https://github.com/clj-commons/clj-yaml/issues/66.