Web servers are notoriously easy to implement with message passing / fork. Threading is a particularly bad model for that case.
Games on the other hand? Oh yeah, you definitely need threads for that.
It's important to note that "multithreading" specifically means shared-memory model of parallel processing. Games are more of an exception than the rule when it comes to being well suited to shared memory.
Isn’t Nginx multithreaded rather than multiprocess? I’m not an expert in web stuff but it’s always felt intuitively that worker threads map nocely into typical web server workloads.
Also, any UI app should basically be multithreaded to prevent interface hiccups.
packetlost|11 months ago
Games on the other hand? Oh yeah, you definitely need threads for that.
It's important to note that "multithreading" specifically means shared-memory model of parallel processing. Games are more of an exception than the rule when it comes to being well suited to shared memory.
andy24|11 months ago
Also, any UI app should basically be multithreaded to prevent interface hiccups.