I think it boils down to how bloated is the C code generated by the C backend, which to some degree has to be, since it's generated programmatically. My undest

I think it boils down to how bloated is the C code generated by the C backend, which to some degree has to be, since it's generated programmatically. My undestanding is what ends up happening is that the wasm step acts as a form of semantic compression that brings its own benefits over zstd (and which can still be combined with zstd by compressing the wasm file).