Originally Posted by FatalKeystroke
I don't know why people are trying to promote forking as a general purpose alternative to multithreading.
As the OP has corretly noticed, those two are (from a developer's standpoint) two completely different things -- even though on Linux they are technically more similar than one would expect or hope for.
Some applications will lend themselves to be done with multithreading, some with multi processes, and some equally well to both.
Then again, some (many?) developers will forever be limited to forking, as they simply cannot wrap their mind around multithreading and its pitfalls.
But an unqualified "use fork()" is just -- wrong.