No, you have to go through a seriously crazy api wherein data is passed into a single managed array in wasm, and pulled off in JS and visa versa.
Ok - so accessing C libs is useful?
Are bindings from other languages to C considered to be really an important things for those languages?
Was there a specific set of libs that we were angling for?
Does it even make sense to do those things in the browser?
And what about the limitations - i.e. having to pass data into and out of the WASM container - does that play well with usage of 'codecs'?
Maybe not.
So why again does WASM exist?
What as the compelling use case?
Flash/UX is definitely not it.
I don't see any real uses cases for things like codes, nor was I seeing demand.
So where is the market/product need? And use case?
This is cool tech that's a long way off from being useful in the real world.
Having gone through the pain of writing my own little app, I realized that it's still fairly bleeding edge. I will go back to it when there are deeper APIs between JS and C, are the toolchain is more stable.