Multithreaded code can be useful on a single core when you have blocking syscalls. Non-blocking I/O can help but doesn't eliminate this. Further, non-blocking

Multithreaded code can be useful on a single core when you have blocking syscalls. Non-blocking I/O can help but doesn't eliminate this. Further, non-blocking I/O carries its own complexities. Though I have to say, your characterization of the issues with multi-threading is nothing short of hilarious.