Honest question: are you so experienced that you've deliberately decided to shun threads in favour of processes, or not sufficiently experienced to have even considered using threads at all?
If you're in the second category, you might want to look in to using threads rather than processes. There are some very real advantages to using processes for concurrency, but doing so is typically more work (especially in C-like languages).
Show differencesHistory of post edits
#1edd²
Posted 25 February 2012 - 03:17 PM
Honest question: are you so experienced that you've deliberately decided to shun threads in favour of processes, or not sufficiently experienced to have even considered using threads at all?
If you're in the second category, you might want to look in to using threads rather than processes. There are some very real advantages to using processes rather than threads, but doing so is typically more work (especially in C-like languages).
If you're in the second category, you might want to look in to using threads rather than processes. There are some very real advantages to using processes rather than threads, but doing so is typically more work (especially in C-like languages).