Hacker News Reader

Once you allow to call Python, keeping things sandboxed becomes pretty hard, doesn't it?

That's true. However, it allows to integrate your Wasm program to your favorite framework more easily. It's likely to be a small surface of code to review carefully. It's always a balance :-).

It's often for code that is asynchronous that will not return an answer immediately... the function passing is most often used to send a callback for these situations.

A state-machine, generator or coroutine can be used instead of callbacks.

I mostly prefer only having one direction of who-calls-who when combining multiple languages. Though I understand that for a general purpose system like Wasmer it makes sense to support everything, so that users can choose the architecture.

Reply on news.ycombinator.com