Benchmarking mir.ndslice + lubeck against numpy and Julia

[Doc Andrew]

On Sunday, 12 January 2020 at 00:25:44 UTC, JN wrote:
>
> Meh. I don't like this kind of table. I think it should at 
> least say "Python/C". Imagine a newcomer encountering this 
> table and being like "wow, D is slower even than Python, what a 
> mess!". But numpy/scipy are running C underneath, so D is not 
> that bad in comparison.

C? Try Fortran! 
https://github.com/scipy/scipy/blob/master/scipy/linalg/src/id_dist/src/idz_svd.f (I think that's the underlying code being called in the OP's example)

But your point still stands. Most of the heavy-duty lifting done 
by Python scientific computing libs is done by carefully-tuned, 
long-standing native code. There's nothing stopping D from 
linking to said libraries...

-Doc