Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I question your belief that concurrency implies the success of a language. Let's consider the case of Erlang. It has the strongest implementation of concurrency. I do not think it has been very succesful. I do not see Erlang adopted everywhere just because it can do concurrency well. In fact, C and C++ are still widely used for it.

There is a well-known myth in the Perl community that threads are the worst possible thing, however that is because Perl programmers which deal mostly with web programming don't study threads well enough so of course they cannot use them. As a retreat, they use POE instead which is not real concurrency.

They hide behind excuses of the form "threads are too complicated for the human brain". That is of course complete nonsense because threads are well studied and can be learned, but what can you ask of web developers who deal with CSS , Javascript, HTML. They concentrate on completely different things.

But let's return to Perl 6, Parrot does not support concurrency. Let us suppose that concurrency will be implemented. Who would use it ? Since most Perl programmers already have the prejudice that threads are evil and bad.

Let's also consider another aspect. As it stands today Perl is mostly used by sysadmins(although I do not like to say this), what use would sysadmins have for concurrency. Most sysadmins are not well-trained programmers.

I think you should not assume oppinions of people who evangelize a language or the other. Instead you should judge them with your own mind and see for yourself if they have been adopted or not.

In reply to Re^9: The current state of Perl6 by Anonymous Monk
in thread The current state of Perl6 by Anonymous Monk

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others rifling through the Monastery: (7)
    As of 2017-08-18 16:38 GMT
    Find Nodes?
      Voting Booth?
      Who is your favorite scientist and why?

      Results (306 votes). Check out past polls.