> That's not a good enough reason not to write multithreaded software Possibly not, but it's a very good reason not to use multithreaded software, when a simpl

> That's not a good enough reason not to write multithreaded software Possibly not, but it's a very good reason not to use multithreaded software, when a simple single-threaded alternative is present. It's a very practical decision in my case: I'd rather rely on something that I know eliminates entire categories of bugs, if performance is acceptable (it is for me). Also, if it breaks, I can dive in, understand it and fix it. Simplicity should not be underrated.