container2wasm

Really impressed by the depth and breadth of this project, well done! A particularly interesting part is the socket layer inside the browser. Other people solving this problem have previously used a proxy to a server that does the real socket implementation. This means you can't have a "browser-only" solution. The author has solved this (for HTTP/S only) by proxying HTTP requests and then re-creating them as fetch requests (details here: https://github.com/ktock/container2wasm/tree/main/examples/n...). I'm very interested in using this approach for my own project Runno (https://runno.dev).

container2wasm > Additional Resources: https://github.com/ktock/container2wasm#additional-resources : vscode-container-wasm: https://github.com/ktock/vscode-container-wasm : > VSCode extension for running containers on VSCode for the web (e.g. github.dev, [vscode.dev,]), leveraging container2wasm Chromebooks can run vscode.dev and WASM. Is this the best way to `git clone` and run `python -m this` in a Bash/ZSH shell on a Chromebook? This could be useful with jupyter-repo2docker.