Excellent point made here.

And it shows a key element of this entire debate. The decision to fork or to thread should be based on need, form and function of the code. In some cases, it's is clear that fork is the better solution, others it is thread. A good programmer / developer will try to have both skills under their belt (though I'm not quite a that level, yet).

Another consideration, though, is the fact that not all systems have Perl threading available. Some systems do not have a version of Perl installed that allows threads, and may not be able to install an outside module that will allow it (like the place where I work). I know that will sound unusual, but consider the fact that some places hold a VERY tight control over what is installed from an outside source. If it is a secure (i.e. DoD, NSA, etc.), the site may not allow additions to the system that way becaused they are not 'blessed' by certain security-minded individuals.

All in all, sometimes the 'better' choice isn't an option. Best to have all the tools you can available in your own head.