3 ms·

WASI is not meant for browsers, it's for using WebAssembly as platform-independent bytecode in non-browser environments.

• skybrian 3y ago
  The article claims they got it working in the browser, but not how.
  • dynamitebud 3y ago
    That'll be added using the @wasmer/wasi npm package. We'll be updating that soon
    • mrkstu 3y ago
      So could one use this to run a fully socket capable Jupyter notebook? There are some infosec dashboards I would like to build, but not having the ability to actually run socket capable code killed the interesting aspect of doing it in the browser.
      • the8472 3y ago
        Browsers don't have TCP/UDP/etc. sockets, so a WASI impl running in one can't provide that either.
        • skybrian 3y ago
          Possibly it could be emulated using a Wireguard bridge? A Tailscale connection might be interesting. Something like: https://tailscale.com/blog/ssh-console/ https://tailscale.com/blog/ssh-console/
          • yuri91 3y ago
            This is exactly what we do in Webvm: https://leaningtech.com/webvm-virtual-machine-with-networking-via-tailscale/ https://leaningtech.com/webvm-virtual-machine-with-networkin...
  • preseinger 3y ago
    wasi -- web assembly system interface -- is explicitly designed for not-browser environments you can hack it into a browser, i guess, but that's subverting the fundamental purpose of the thing
    • tokera 3y ago
      i dont think Linus intended his operating system code to land rocket ships on barges either but hey... we can forgive him.