wow a python interpreter is "only" 100MB not sure if that's what's happening here
Show HN: WASM-powered codespaces for Python notebooks on GitHub
11–20 of 30 posts
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#12wow a python interpreter is "only" 100MB not sure if that's what's happening here
Is that too small or too large in your estimation?
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#13Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#14Super cool to see a real use-case of WASM outside of just game dev and nerding out.
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#15> Notebooks created from GitHub links have the entire contents of the repository mounted into the notebook's filesystem. This lets you work with files using regular Python file I/O!
Could BusyBox sh compiled to WASM (maybe on emscripten-forge) work with files on this same filesystem?
"Opening a GitHub remote with vscode.dev requires GitHub login? #237371" ... but it works with Marimo and JupyterLite: https://github.com/microsoft/vscode/issues/237371
Does Marimo support local file system access?
jupyterlab-filesystem-access only works with Chrome?: https://github.com/jupyterlab-contrib/jupyterlab-filesystem-...
vscode-marimo: https://github.com/marimo-team/vscode-marimo
"Normalize and make Content frontends and backends extensible #315" https://github.com/jupyterlite/jupyterlite/issues/315
"ENH: Pluggable Cloud Storage provider API; git, jupyter/rtc" https://github.com/jupyterlite/jupyterlite/issues/464
Jupyterlite has read only access to GitHub repos without login, but vscode.dev does not.
Anyways, nbreproduce wraps repo2docker and there's also a repo2jupyterlite.
nbreproduce builds a container to run an .ipynb with: https://github.com/econ-ark/nbreproduce
container2wasm wraps vscode-container-wasm: https://github.com/ktock/vscode-container-wasm
container2wasm: https://github.com/ktock/container2wasm
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#16The Godot docs mention coi-serviceworker; https://github.com/orgs/community/discussions/13309 :
gzuidhof/coi-serviceworker: https://github.com/gzuidhof/coi-serviceworker :
> Cross-origin isolation (COOP and COEP) through a service worker for situations in which you can't control the headers (e.g. GH pages)
CF Pages' free unlimited bandwidth and gitops-style deploy might solve for apps that require more than the 100GB software cap of free bandwidth GH has for open source projects.
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#17> CORS and GitHub The Godot docs mention coi-serviceworker; https://github.com/orgs/community/discussions/13309 : gzuidhof/coi-serviceworker: https://github.com/gzuidhof/coi-serviceworker : > Cross-origin isolation (COOP and COEP) through a service worker for situations in which you can't control the headers (e.g. GH pages) CF Pages' free unlimited bandwidth and gitops-style deploy might solve for apps that require m…
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#18wow a python interpreter is "only" 100MB not sure if that's what's happening here
It is much smaller than that, Pyodide is only 2.8mb and the Python stdlib is 2.3mb when zipped
https://www.reddit.com/r/Python/comments/1huxrs6/python_runn...
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#19Earlier quoted context omitted.
It is much smaller than that, Pyodide is only 2.8mb and the Python stdlib is 2.3mb when zipped
There is $300k in bounties if you create under 1MB WebAssembly CPython distribution https://www.reddit.com/r/Python/comments/1huxrs6/python_runn...
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#20I really like Observable as well, but I've found it difficult to find robust and broad numerical libraries in javascript like what Python has.
I would love for this type of tool to redefine how we do science. It would be amazing if many scientific papers included both their data and the code in an interactive environment with zero installs and configuration. Plus when discussing a paper you could "fork" it and explore different analysis options live which for many fields would be totally feasible to do in the browser.