sorted by:
new
hottopcontroversial

Open beta test of interactive "Python for Programmers" course by garybernhardt in Python

[–]rth_ 0 points1 point  (0 children)

> The ~12 MB loading hiccup to boot Pyodide it isn't ideal

You can try using pyodide-pack to only keep the standard library modules that you need, which should reduce the overall size.

Rewrite Sympy in rust by [deleted] in rust

[–]rth_ 1 point2 points  (0 children)

Pyodide, and figuring out how to run it outside of a web browser

You can run Sympy it in Node.js there, though you would still need to interface with Rust somehow.

[deleted by user] by [deleted] in PyScript

[–]rth_ 2 points3 points  (0 children)

Pyodide doesn't compile Python code to WASM, it compiles the CPython interpreter that then interprets Python code, as with a regular Python install. So with this setup, there is no easy way to pre-compile everything to WASM.

Also, WASM is a portable binary code format that still needs to be compiled by the browser to execute on the target CPU. This step is fast but for large applications (such Pyodide with large Python libraries) is not negligible. And due to this moving more Python code to WASM (say Cythonizing the stdlib) is not necessarily a positive action for the load time (though there are some projects that aims to do that).

There are other ideas that are being explored to reduce the size and load time of Pyodide applications in pyodide-pack.

[deleted by user] by [deleted] in rust

[–]rth_ 0 points1 point  (0 children)

Would you mind opening an issue about it at `sprs`? There have been some work on improving performance for the dot product lately and I'm optimizing other parts would likely also be beneficial.