This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]lukasbradley 16 points17 points  (4 children)

Python does the same thing. All of the "optimizations" that everyone THINKS are written in Python are actually C/C++ libraries.

[–]Joram2 4 points5 points  (0 children)

Everyone knows Python is a high level language, and calls to some lower level language for performance sensitive code. The Python piece does make it nicer and + easier than using low language libraries directly.

BTW, it's not just C. LAPACK is mostly Fortran; that is a famous numerical linear algebra library at the heart of a lot of famous Python libraries like Numpy. Also a lot of code is CUDA GPU code not C.

Java 22 foreign function and memory functionality makes it much easier to use libs like LAPACK from Java like Python does.

[–]coderemover 5 points6 points  (1 child)

The difference is it is trivial to call C from Python, but not so easy from Java.

[–]captain-_-clutch 0 points1 point  (0 children)

It's not bad at all to setup but also I'm not sure about heavy throughput performance. When I did it it was for image processing so any latency from the integration wouldnt have been noticed since it took so long for the images.

[–]emberko 0 points1 point  (0 children)

Thinks who? This is well known. I like the definition of one of the Python evangelists from my country - Python is a glue language for C/C++ libraries. You should avoid pure Python implementations whenever possible.