[yuri91]

I am curious about the browser compatibility layer.

Does it support networking? (And if so, is it using a proxy to connect to the internet or is it using a virtualized network layer that stays in the browser?)

How is fork implemented? (Asyncify all the code?)

I was looking at the Github org page (https://github.com/wasix-org), but I can't figure out where this stuff is.

[preseinger]

wasi is wasm applied outside of the browser

it's basically nonsensical to try to adapt wasi in the browser

[yuri91]

I don't necessarily disagree, but implementing these things in your custom runtime is easy. I am more interested in how they achieved them in the more constrained browser environment.

[skybrian]

They claim they did it. That's what we're talking about. Did you read the article?

[preseinger]

i'm sure they did it, that's fine

my point is that this is a nonsensical thing to do

[tokera]

its only nonsense from ones perspective... from another perspective it makes a lot of sense - if one wants to create a fully sandboxed browser terminal (benefits of which are huge). then compiling bash to WASM goes a long way as who wants to rewrite all that terminal code anyway?

https://wasmer.sh/

[preseinger]

syrus sockpuppet be gone

[tokera]

glad you like my sock(et) work indeed

https://github.com/john-sharratt/wasix-witx/commit/3b1469687...

now I know its hard to imagine someone other than your personal boogeyman contributing value to the open source world, but there is a real need for me to keep my coding skills up to scratch and it just so happens that `wasmer.io` are the coolest kids in WASM town right now, so I'll share my spare time with them thanks.