Bad threading behaviour in perl isn't much of a problem these days. Listening to my managers/salespersons/cleaning staff, these days you do most stuff "in the cloud" (e.g. as webservice) anyway. And on webservers you don't thread, you fork 8-)

More seriously: I my opinion, the best way to choose is to learn the *basics* of both and try to code small routines you would need in your project. The language that causes the least hairloss (or grey strains, whatever rocks your genes) will be the language of choice.

In reply to Re^2: I want to know the problems in Perl by cavac
in thread I want to know the problems in Perl by maheshgupta024

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.