News for hackers. Stuff that matters.

A comment on Pythran as a bridge between fast prototyping and code deployment.

Re:Pythran as a bridge between fast prototyping and code dep... by kristofferc on Thursday November 29, 2018 @12:09PM (#18561739)
I feel that a comparison to the handwritten C++ version would make the claims a lot stronger. Making something 10x faster is not very hard if it is incredibly slow to begin with and is, on its own, fairly uninteresting. On the other hand, if the results here approcahed the speed of optimized C++ code, then this workflow makes a lot of sense.
[ Parent | on HN ]
Re:Pythran as a bridge between fast prototyping and code dep... by SubiculumCode on Thursday November 29, 2018 @03:37PM (#18563749)
Seems there could be a cost/benefit analysis here. Ten times faster than python might be sufficient for some applications given the potential for much faster deployment, regardless of whether handwritten C might be faster.
[ Parent | on HN ]
Re:Pythran as a bridge between fast prototyping and code dep... by jeanl on Thursday November 29, 2018 @06:07PM (#18565025)
You're absolutely right: you don't necessarily need to be within 10% of pure C++ if algo development is made far easier by using python/numpy. But it would be good to have a hand-written C++ baseline to determine where the cost/benefit point is (at least for this example).
[ Parent | on HN ]
Re:Pythran as a bridge between fast prototyping and code dep... by jeanl on Thursday November 29, 2018 @12:32PM (#18561934)
That's a fair point and I have to admit I didn't have the time/courage to port the entire algo to C++. But I can see why that would make the results a lot more convincing.
[ Parent | on HN ]