<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">* How does your language handle scalability issues?<br></blockquote>
<div><br>I don't even know how to frame that question.<br><br>An answer could be something like "well" or "poorly", or it could be countered with a question like "what do you mean by 'scalability'?" Because the follow-up questions seems to deal with concurrent streams of execution... is this the very definition of 'scalability'?<br>
<br>If so...<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
* Applications that require many concurrent threads of execution?<br>
* How does the language interact with threading?<br></blockquote><div><br>(list the various core Perl threading libraries here... see "<a href="http://perldoc.perl.org/Thread.html">http://perldoc.perl.org/Thread.html</a>" as a starting point)<br>
<br>Also, various CPAN threading extensions exist, like POE (roughly equivalent to "Twisted" in Python-land), and "Coro".<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
* Does it offer other models for managing concurrent processing?<br>
<br></blockquote><div><br>How about the good old Unix fork/exec model? That's still the standard way of doing such things in Perl. However, there is a wonderful CPAN module called "Parallel::Iterator" which makes mananging child processes via the fork/exec module at least as easy as dealing with threads is in other languages.<br>
<br>Cheers,<br> - Richard<br><br></div></div>