"To overcome these self-inflicted challenges, DolphinDB stopped hiring noob developers trying to make HFT systems in Python, instead preferring run-of-the-mill C/C++ developers who understand heap vs stack allocation".
Edit: oh wow, check the poster's previous submissions :)
RobRiveraβ’about 2 hours ago
Thanks for saving me a read.
I love the open-ended nature of the title tho.
It doesn't say how an effective, efficient, nor industrial low-lantency engine works, nor what a microsecond level engine is (insofar as a label cutoff).
Honestly, boring heap/stack practices with mindfulness about the application workflow and memory management therein goes miles.
jeffbeeβ’about 2 hours ago
That certainly is a bag of words. I'll congratulate anyone who can convincingly explain why the TCMalloc design diagram is in this blog post.
laweijfmvoβ’about 2 hours ago
i'm still trying to figure out why the Eiffel tower is featured in the first graph
hylarideβ’about 2 hours ago
This article feels like it was "expanded" with an LLM.
Discussion (0 Comments)Read Original on HackerNews
"To overcome these self-inflicted challenges, DolphinDB stopped hiring noob developers trying to make HFT systems in Python, instead preferring run-of-the-mill C/C++ developers who understand heap vs stack allocation".
Edit: oh wow, check the poster's previous submissions :)
I love the open-ended nature of the title tho.
It doesn't say how an effective, efficient, nor industrial low-lantency engine works, nor what a microsecond level engine is (insofar as a label cutoff).
Honestly, boring heap/stack practices with mindfulness about the application workflow and memory management therein goes miles.