If Parrot is significantly more embeddable than Perl (and that doesn't take much!), then it will be highly relevant to me. I have a system for which we hope to get 3rd party developers to produce content. When I needed to add a scripting language, I chose Perl because of CPAN and my personal familiarity with it. It has proven to be a major PITA getting it to really work well with C++, and Perl is limiting my potential audience drastically. For applications like this, Parrot would be a lifesaver: better embeddability, and multiple front-end languages.

I suspect we'll see a working Python, Ruby, PHP, or Tcl front-end well before Ponie or Perl6, btw. They're smaller and more regular.

Update: by "regular" I mean the definition "orderly, even, or symmetrical" (from dictionary.com). Fewer exceptions, more orthogonality. Python seems to be built from a small handful of concepts that you constantly reuse and build ever higher towering edifices of abstraction and bothersome structure. Ruby picks a slightly different set of basic constructs, and provides more opportunity to be concise when you want to, but still has fewer special cases and shortcut constructs than Perl. PHP seems to gain regularity by discarding some of the more irregular parts of Perl. Tcl, at least the one I used many years ago before they object-ified the internals, was a tiny, simplistic string-based language. The core language was very regular, although the various things built atop that core were all over the place. But for Parrot, only the core really matters.

Note that I was not using "regular" as a value judgement. I really like many of Perl's irregularities, although (especially when you're implementing or embedding a language) there is a lot to be said for minimalism and regularity too. I don't think Perl has gotten the balance exactly right, nor have I encountered any other language that feels to me that it might.

Sorry for doubling the length of this node with an update, but I wanted to respond to sth's reply, but the response felt more like a clarification than an independent node.

In reply to Re^2: Parrot, the future of dynamic languages ? by sfink
in thread Parrot, the future of dynamic languages ? by szabgab

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.