Case by case situation. WASM is nothing but a spec and impl for CPU tasks. If you want to do something like networking, you call out to JS (today). If you want

Case by case situation. WASM is nothing but a spec and impl for CPU tasks. If you want to do something like networking, you call out to JS (today). If you want to decode JSON, you could call out to JS, or populate some part of the WASM-accessible mem (a byte array) and then ask WASM to operate on it. It could be a C library compiled to WASM or hand-written or in some other compile-to-WASM lang.