Safety not important in HFT? You'd better make sure those precious microseconds buy you enough to make up for when things go awry.

Also, modern online gaming with microtransactions isn't something I'd entrust to "hold my beer" languages and gaming industry development practices.

Crashes from safety bugs are rare in HFT because they can replay years of data against code changes. For a strategy that trades in and out of positions quickly and is flat most of the time, it's also often not a big deal if the program crashes in the midst of running, as long as some technique has been arranged to cancel resting orders and alert a trader (who is generally monitoring the system's operations at all times).

They're certainly not inclined to pursue safety at any expense of performance in their code.

>Safety not important in HFT? You'd better make sure those precious microseconds buy you enough to make up for when things go awry.

Memory safety bugs are very rare in modern, well-written and tested C++. The key difference is that there are no adversarial inputs, while something like a browser or server needs to deal with potentially adversarial inputs, making absolute memory safety much more important (as even a single memory safety issue could be exploited).

> modern online gaming with microtransactions

I don't think anyone should develop such games either