While you'll need a parrot install as well as the bytecode file, that's still a darned sight better than what we have now with perl, where it's "Install perl. Install these X modules from CPAN, install this whole dir tree of stuff for my app."

End deployment should be as simple as possible. A single file deployment is best, but barring that a persistent environment (like the JVM or parrot) that doesn't need to change with a single file for the app's not bad either.

And I am taking a shot at being able to build a single-file combined interpreter and bytecode app, though it might be large... :)

In reply to Re: Re^3: What is the big deal about PAR(rot)? by Elian
in thread What is the big deal about PAR? by Anonymous Monk

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.