2 ms·
Sure, but it's an avoidable problem. Writing multithreaded code on a single core is like saying to the OS: "I don't know what order I want my code to execute,
by axod 17y ago
Sure, but it's an avoidable problem.
Writing multithreaded code on a single core is like saying to the OS:
"I don't know what order I want my code to execute, here! You decide some random pattern, and I'll write a ton of code to deal with your random execution of my code."
- djcapelis 17y agoMultithreaded 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.
- jacquesm 17y ago> "I don't know what order I want my code to execute, here! You decide some random pattern, and I'll write a ton of code to deal with your random execution of my code." Writing like that makes me jealous. There is so much insight in that one line, it shows how much you've done better than any long exposition ever could. That level of brevity is something to aspire to, maybe one day...