4 ms·
wasi is wasm applied outside of the browser it's basically nonsensical to try to adapt wasi in the browser
by preseinger 3y ago
wasi is wasm applied outside of the browser
it's basically nonsensical to try to adapt wasi in the browser
- skybrian 3y agoThey claim they did it. That's what we're talking about. Did you read the article?
- preseinger 3y agoi'm sure they did it, that's fine my point is that this is a nonsensical thing to do
- tokera 3y agoits 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/ https://wasmer.sh/
- preseinger 3y agosyrus sockpuppet be gone
- tokera 3y agoglad you like my sock(et) work indeed https://github.com/john-sharratt/wasix-witx/commit/3b14696876579bd83877751f14e6fd9347db9204 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.
- preseinger 3y agowasmer has a well-documented history of malicious behavior, they are very clearly not the coolest kids in WASM town, and very clearly not who you want to be aligning yourself with, but of course do whatever you like :shrug:
- yuri91 3y agoI 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.