Not a great proposal IMHO and it misses the point of wasm in general. Strings and other high level data structures are distinctions the high level languages that output wasm should make. Anyone who's had to do java to .net clr interop will say how problematic it was. The only resonable way to do it was via text de/serialisation on the database or via a web based api, even on the same computer. That's crazy when you think about it.

So arrays of numbers will work and have predictable performance from one wasm runtime to another.

Personally, I'd prefer to see wasm not repeat the same disasterous mistakes Java made.

Whats the status on this? How long before the component model is something we can use?