2 ms·

Insightful writeup! I am just not sure what did you mean to discourage in part A. > A) If you're writing high-performance code DON'T you _will_ hit bottleneck

by O_H_E 5y ago

Insightful writeup! I am just not sure what did you mean to discourage in part A. > A) If you're writing high-performance code DON'T you _will_ hit bottlenecks which are non-trivial to the language unless you're a guru. DON'T do what? don't try to hyper-optimize your code? don't use all types of "fancy" constructs like how the post shows?

rob_c 5y ago
Don't write code designed to burn CPU with numerical calculations. There is hyper optimisation and then there is the right tool for the job. The speed loss from doing mathS in an interpreter is huge and frankly usually not worth paying. Python like this is great for low CPU hyper responsive code, or for increasing efficiency of existing constructs. As a rule of advice to anyone who asks me this, go away and read about the benefits of compiled over interpreted code. There's to much to conver in 30s and frankly if you're worrying about extreme performance you shouldn't be using python... That's not too say I don't think python is awesome, but, write a module in something else :p