Hacker News Reader

It is already faster because there is no lock congestion.

It's very hard to not accidentally pull in a dependency that makes your code multithreaded.

You guys could argue this all day and both be right. Depending on what type of system you're working on, you are either very likely to pull in a multithreaded dependency or you are not. Systems programming is different from game programming is different from web client programming is different from kernel development. In most of my career, I would have never accidentally pulled in a multithreaded dependency, but I could see how that could be easy to do in some cases.

For this use case a good copying collector would be best. Beats any malloc by miles.