Code review comment for lp:~vanvugt/mir/mirout-save-load

> alright as is, although I've forgotten why we need MirBlob as part of the
> client api at all. Seems it would be be better for this client to come up with
> its own data format (csv? xml?) than rely on mirblob.
>
> Suppose, needs discussion on that point, otherwise lgtm

The requirement comes from a compromise at a sprint a couple of years ago.

Downstream didn't want to deal with tracking any changes to the display configuration information or backward compatibility for the serialized form. So we had to provided one.

Despite the urgency and shouting I don't think they ever got around to using it. So we could probably drop it for 1.0.