On Fri, 2019-09-27 at 13:52 +0100, Daniel P. Berrangé wrote: > The really big difference though is that I replaced the use > of XML data files with YAML data files. This was done with > the aim of making the data more human friendly. XML is really > optimized for machines, not humans, so writing the data files > was not pretty. YAML is optimized for human readability, and > is actually even easier to consume in Go than the XML was, > so its a double win. I'll add my own 0.2 $currency to what others have said. I think Go is a fine language to use for this kind of tool, so I'm in favor of that; having a more granular view into the details of the system also looks like a good idea. What I'm not sold on is the advantage of a YAML-driven approach: it seems to me that the same result could be achieved much more conveniently using regular Go code instead. Perhaps it would be useful if you explained in detail why you decided to take this approach in the first place. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
