go_js_wasm_exec icon indicating copy to clipboard operation
go_js_wasm_exec copied to clipboard

Published 20 hours ago • verified publisher icon neelance

Different IO

Open backkem opened this issue 5 years ago • 0 comments

The example currently allows writing to a file (stdout). I wanted to explore how this could support additional types of IO.

Networking For use cases like services it would make sense to interact over the network. However, it the current GOOS=js build target doesn't support networking. In addition, there is no standardized WASM syscall interface, making it hard to define what a new build target would look like. CraneStation/wasmtime seems to have picked CloudABI for this. That may offer a viable option.

Custom entry points For use cases like serverless, blockchains, data pipelines, ... it would make sense to interact over custom entry points. To make these possible, it may be worth reevaluating the discussion in golang/go#25612.

backkem avatar Dec 26 '18 18:12 backkem