4 ms·
you can but through a python interpreter in the mojo process so you get the same numpy speed with mojo<->ptyhon interop overhead. NuMojo is native and also is n
by MohamedMabrouk 2mo ago
you can but through a python interpreter in the mojo process so you get the same numpy speed with mojo<->ptyhon interop overhead.
NuMojo is native and also is now starting to support features that numpy can't really do like native GPU execution.
- vovavili 2mo agoI wonder if the Python-to-Mojo overhead is significant enough where language-native bindings make more sense. I'd be interested in seeing some benchmarks.
- deleted 2mo ago[deleted]
- ch4s3 2mo ago> numpy can't really do like native GPU execution I'd be interested to see where GPU code beats NUMPY's SIMD implementation, which is really
- deleted 2mo ago[deleted]
- insane_dreamer 2mo ago> features that numpy can't really do like native GPU execution we use numpy + jax for that; works well