I would prefer this over JSON.

For Ziggy to be competitive vs protobuf it would need more machinery for managing schema changes, which currently is not there at all.

I'm currently writing an application where I'm doing binary serialization of data and I'm not sure yet how that should play into Ziggy, but as I explore my use cases more I will change Ziggy accordingly.

That said, I will probably always err on the side of small scale, so it might very well never become a format worth considering vs protobuf. We'll see.