I don't think this needs to be an "either/or" type of scenario. Depends on the specific requirements. Sometimes you need a multi-threaded model...i think a GUI

I don't think this needs to be an "either/or" type of scenario. Depends on the specific requirements. Sometimes you need a multi-threaded model...i think a GUI library is a good example of that. Other times, a multi-process model would be easier to set up...a "just run in the background" sort of thing. I also don't quite understand why suddenly everybody is afraid of writing multi-threaded applications. Just make sure you understand how the threading model works in your specific technology and what abstractions are provided. If your application is complex enough to require a "complex algorithm to manage shared memory", then i think you need to really take your time to understand what you're trying to do. Having said that; I acknowledge that chasing down bugs caused by threads is not fun at all. Especially race conditions since they are seemingly un-predictable. But i think it is getting easier with newer platforms and tools.