[phyrrus9]

It proves that any slowness in your program while using Python is not from Python, and just your bad programming.

The easiest way to disprove this with proof is by using the NumPy Python package, which is used for mathematical computations. It is *exceptionally* popular.

And guess what... The mathematical computing is done in C, which is compiled as a library and used as part of the Python package. If Python _wasn't_ slow, then the package wouldn't require C. If Python's slowness _only_ came from the skills of the programmer, then surely a handful of thousands/tens of thousands/hundreds of thousands of Python developers using NumPy would have transitioned the package away from C... But the spoiler is this: NumPy _is only popular_ due to its efficiency of 1) mathematical computing, and 2) ability to _not_ be slow.

NumPy would never be popular if it was fully implemented in Python. And the NumPy core contributors/original authors know this, and this is why Python uses C, as a result of _Python being slow_.

But instead of reading and NOT BEING IGNORANT, I bet you read the title amd a few comments, then high holstered that ego of yours. Please step down, lol. I haven't seen such ignorance while saying don't be ignorant.

I actually read the Q/A thread*** (not an article), and I found some points valid and some points invalid. If your crutch is that you think Python is only slow due to the coder's abilities to write _good_ Python, then you have completely glossed over many core computer science fundamentals, and _this_ is where your disconnect is.

I do not have an ego about Python; I actually like the language. I use Python at work, and have made a handful of FOSS projects with it. I enjoy Python, but _it is *extremely* slow_ when compared to other languages. Python _is not slow_ because of the developer, Python is slow because it is uses an interpreted environment with garbage collection and other high-level mechanisms. Yes, Python can be improved _a bit_ (for the love of God, switch to a modern versions and use f-strings), but it can only be improved so much.

Also, if you want to do some research into the Cython language, you'll find something new to chew on (that you may actually find interesting _and_ compelling). Code as you wish, though; the best study is one that uses only a single sample.

as for the first paragraph, that's a stupid argument. It doesn't require C, it was written in C. There's a huge difference between the two. Odds are the library was written for something else and simply adapted to also have python bindings.

Python is slow because it is uses an interpreted environment with garbage collection and other high-level mechanisms

exactly this. Every programming language ultimately makes its way down to machine code. Languages like C and Go compile it down to machine/asm, optimize that, then assemble it. Languages like python are supported by a large runtime (in machine code) that's pre-programmed to do x when it sees y. This is inherently slower.