> It's usually better to write single-thread code and avoid multithreading except in few carefully written places. implies that you did have some problem with

> It's usually better to write single-thread code and avoid multithreading except in few carefully written places. implies that you did have some problem with multithreaded code, which is why you ultimately chose to avoid it. Stuff like rayon in Rust lets you sprinkle multithreading over your codebase very easily without needing to worry at all, because Rust keeps it safe. > but its memory management model is much harder to use IME it takes some getting used to but once you do it's pretty automatic and you don't have to think about it much. YMMV.