2 ms·
"Fast" is a bold claim, given the complete lack of benchmarks and the fact that it's written entirely in Python...
by 749402826 2y ago
"Fast" is a bold claim, given the complete lack of benchmarks and the fact that it's written entirely in Python...
- paddy_m 2y agoI'm certain the host heavy lifting is done by numpy which is a python wrapper around Fortran and C. The visualization heavy lifting is done by pygfx/wgpu-py. wgpu-py has C. I think wgpu-py compiles to WASM to run in the browser. More and more packages are taking this route. [1] https://github.com/pygfx/pygfx https://github.com/pygfx/pygfx [2] https://github.com/pygfx/wgpu-py https://github.com/pygfx/wgpu-py
- almarklein 2y agoAll true, except the bit that wgpu-py compiles to WASM. It's all desktop. In the plans that we do have for running the browser, Fastplotlib, Pygfx and wgpy-py will still be Python, running on CPython that is compiled to WASM (via Pyodide). But instead of wgpu-py cffi-ing into a C library, it would make JS calls to the WebGPU API.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- kushalkolar 2y agoIn fastplotlib at the end of the day everything is wgpu under the hood, and as the other poster correctly pointed out about numpy being fortran and C wrappers.