Data model: Why use go-serialized data?

Timeline

hoijui (hoijui) opened

I liked reading the data model! made me dream.. thank you! :-) but I was wondering, why you chose to store Operations/OperationPacks as go-serialized data, instead of an open format like JSON/YAML/Turtle or the like. As much as I can see, this (together with a missing data-model-version) is the only thing that limits other software using the same data-model. The only reason I could imagine, is performance. Did you make benchmark comparisons?

hoijui (hoijui) commented

ahh thanks! Indeed (at least to me) the documentation is unclear then (or outdated). I will try to formulate it so it reflects this.

Michael Muré (MichaelMure) closed the bug