1 min readJul 28, 2020
- Interface types are basically a way of embedding metadata into a wasm file so that arbitrary data types that cannot be represented in pure wasm like strings can be created and exchanged. These differ from waPC in that waPC is expressly concerned with not requiring knowledge of memory models or allocation across the guest-host boundary. waPC calls are supposed to be stateless.
- waPC and waSCC on top of it make no demands of the binary payloads they use. However, the language targeting wasm needs to be able to round trip that data. When it comes to protobuf, this requires reflection support in the language and so that prevents languages like tinygo and assemblyscript from being able to use protobuf. This is why waSCC uses message pack because more languages can compile message pack serializers to wasm.
