🇳🇱
Have I mentioned yet today how much I hate python multiprocessing, or writing cpu-limited algorithms on python in general... my god why could they not fix the GIL lock problem in python3, are the devs really this lazy!
#programming #Python #algorithms #multithreading #threads #threading #Python3
Isn't needing processor power normally what causes a migration to say C from python? That said, I feel your pain. But I'm curious to understand why your wrestling with python on it's weaker fronts?
@musingsole Largely because python offers a suit of tools that make the peripheral work much easier. All the greatest algorithmic trading tools appeared to be in python.
That said python can (as I recently did) acheive the performance, its not incapable of it. It just makes the process more painful than it needs to be in other languages.. even another high level language that allows for easier shared variables between threads would have solved the problem.
The idea that C is noticeably more performant is a bit of a myth. I code in C often and there are many good reasons to pick C, namely low level access to hardware, and it is the more direct and natural way to do GPGPU for certain types of algorithms... but outside of those two points it really isnt something I would pick for performance reasons as you really arent going to see any noticeable performance gain from C over many other high level languages **if** you code it right.
