I have to agree I missed things a bit there :-( forks are simply a better way of dealing with threads then the default perl ithreads, the benefits forks offer goes far beyond the minimal drawbacks. By now the notes about modules that still insist on using threads rather then forks will for most users just be informative as the better solution has been available for long enough for most module maintainers to switch.
On Thu, Feb 10, 2011 at 11:05 AM, Dr.Ruud <rvtol+use...@isolution.nl> wrote: > On 2011-02-09 14:03, Rob Coops wrote: > > > But any developer that tells you that threads are not worth the > > trouble they cause or anything along those lines is clearly an > > experienced programmer who unfortunately has not realized yet > > that the computer world has changed incredibly over the past > > few years. > > Rob, from your reply I understand that you didn't pick up that it is about > the forking/threading difference. (So it is not about doing things in > parallel or not, as you seem to think.) > > This discussion is about why threads are (mostly) wrong, and forks are > (basically) right, when it comes to parallelization. > > -- > Ruud > > > -- > To unsubscribe, e-mail: beginners-unsubscr...@perl.org > For additional commands, e-mail: beginners-h...@perl.org > http://learn.perl.org/ > > >
