The future is awesome. Thanks for building this!
Show HN: WASM-powered codespaces for Python notebooks on GitHub
21–30 of 30 posts
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#22I love seeing projects like this. When Pyiodide came out I was excited but it was a bit difficult to use, this looks and feels fantastic. I 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 an…
I feel like pytomls and shared source are becoming standard, but yes-
notebooks vs research code are sometimes very separate, very difficult to directly reproduce. A big difficultly with "working out of the box, shared in browser" is that weights, training, inference, simulations- are all still very compute intensive.
BUT the nice thing about a stateless notebook, is that you can precompute values- and cache them. I've been really excited about expanding marimo's caching system, and would love to get to a point whether sharing a notebook means being able to run the research yourself without some big setup dance.
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#23Nice ! Is it possible to connect to an in browser DB like WASM DuckDB https://duckdb.org/docs/api/wasm/overview.html or https://github.com/babycommando/entity-db ?
That would be most useful imho !
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#24Nice ! Is it possible to connect to an in browser DB like WASM DuckDB https://duckdb.org/docs/api/wasm/overview.html or https://github.com/babycommando/entity-db ? That would be most useful imho !
duckdb works — just import duckdb. We also have built-in SQL cells, powered by duckdb, which should also work.
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#25Earlier 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...
50k for the 1mb challenge. The rest is to build out the tooling. It looks like they want to run existing ML python libs from within the NEAR blockchain environment.
Wondering why they don't separate concerns here.
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#26Earlier 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...
will the Python ecosystem feel the need to "tree shake" its way to small bundle sizes? Its easy to eliminate tk and turtle graphics, but if a project uses foo.bar.x its hard to determine if rest of foo can be eliminated. JS kinda solved that problem.
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#27Nice ! Is it possible to connect to an in browser DB like WASM DuckDB https://duckdb.org/docs/api/wasm/overview.html or https://github.com/babycommando/entity-db ? That would be most useful imho !
duckdb works — just import duckdb. We also have built-in SQL cells, powered by duckdb, which should also work.
can I config sql cells to use different data source (remote DB/APIs) instead of local duckdb?
Re: Show HN: WASM-powered codespaces for Python notebooks on GitHub
#28This is an awesome, and as a bonus I learned about a mature reactive notebook for python. Great stuff.
The data sharing is awesome. I previously used Google Colab to share runnable code with non-dev coworkers, but their file support requires some kludges to get it working decently.
I know I should just RTFM, but are you all working on tools to embed/cross-compile/emulate non-python binaries in here? I know this is not a good approach, but as a researcher I would love to shut down my server infrastructure and just use 3-4 crusty old binaries I rely on directly in the browser.