No it's basically "how to analyse and improve the performance of Rust code" with a "btw, I prototype in python".
Roughly half the article could have been done without leaving python though. I don't know if python has a good bitset implementation, but at the very least everything before that could have been done in python. So it is more "comparing manually optimized code against unoptimized crap"
Yeah, then there is the implementation thing, if cython or PyPy have been used instead.
The difference between baseline Python and baseline Rust is only 8x here, because most of the heavy lifting in the Python version is done by native code.
"interpreted language" and "compiled language" are category errors.
True, but since the same example can't be done with a Rust based bytecode interpreter, or a Python AOT compiler, due to lack of implementations to use for benchmarking purposes, the remark remains valid.
If you insist.
are what?
Properties assigned to things which cannot have those properties. "Colourless green ideas sleep furiously" has many such errors for example.