We already have those two different sets of people happily using Perl 5. I don't see how Perl 6 is going to be much different on that subject.

As for PL/I, it might actually have succeeded had it been an open source language. But PL/I was too complicated to reimplement in an age where reimplemention was the only way to port it.

Not that I like PL/I all that much. As far as I know, Perl only borrowed one feature consciously from PL/I, which is the ability to iterate over a list of values. In many respects PL/I was not a well-integrated language, and it also didn't have the benefit of several decades of language research to draw on. PL/I did most things in an almost right way, from a modern perspective.

In reply to Re: Re: My Strategy for Perl6 by TimToady
in thread Perl6 syntax being too much complex? How we will teach and read that?! by gmpassos

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.