News for hackers. Stuff that matters.

A comment on JNumPy: Writing high-performance C extensions for Python in minutes. Parent comment

Re:JNumPy: Writing high-performance C extensions for Python ... by anewhnaccount2 on Wednesday August 10, 2022 @02:15AM (#32408332)
It is happening: https://github.com/faster-cpython/ideas
[ Parent | on HN ]
Re:JNumPy: Writing high-performance C extensions for Python ... by TekMol on Wednesday August 10, 2022 @02:43AM (#32408480)
It seems to indicate a 30% performance boost?

That would be a step into the right direction.

6 more 30% improvements and it is on par with PHP.

[ Parent | on HN ]
Re:JNumPy: Writing high-performance C extensions for Python ... by lraxl on Wednesday August 10, 2022 @04:18AM (#32409155)
It will yield a small speedup (< 50%) at best, probably for selected benchmarks that will be widely promoted.

Microsoft is misallocating its resources. The scientific ecosystem should be ported to .NET, with first class support for F#.

[ Parent | on HN ]
Re:JNumPy: Writing high-performance C extensions for Python ... by jeremycarter on Wednesday August 10, 2022 @06:15AM (#32409793)
.NET would be the perfect ecosystem. And for those who love their dynamic there is support for that too.
[ Parent | on HN ]
Re:JNumPy: Writing high-performance C extensions for Python ... by machinekob on Wednesday August 10, 2022 @05:30AM (#32409547)
They already try it like 2/3 times and it didnt take off so why should it be different today?
[ Parent | on HN ]
Re:JNumPy: Writing high-performance C extensions for Python ... by melony on Wednesday August 10, 2022 @10:50PM (#32420979)
Everytime they did it, it was half baked at best. Scientific libraries need driver support, Microsoft always takes the happy path and ignores all the other hardware permutations. If you are not running Intel/Nvidia in a Win32 environment you are out of luck. WSL2, ARM, AMD, etc. don't have much synergy in terms of product support.
[ Parent | on HN ]