We can:
-
Wait for that to happen (will happen < 1 year, I would bet for certain)
-
Build a bridge to Rust (where the runtime has WASI networking), and have our r3.wasm built as a Rust project that embeds Ren-C.
-
I like Rust, and want a Rust bridge, Shixin started one that I have only glanced at; I know a lot more Rust now than then.
-
The "weird" Rust toolchain isn't necessarily any weirder than a "weird" clang wired up to target WASI, so on the topic of dependencies it's actually a thought-out thing that has some various virtuosities.
-
-
Have me contribute to Wasi-SDK or Emscripten and write it myself:
-
This is a bad way to burn my cycles on something that will happen anyway.
-
The Rust bridge would be a much more forward looking idea
-
So default is (1), but maybe (2).