That's a problem yea. People go after what they know. Since I've been testing PAR, perl2exe out, I have some experiences. :)

Sure, they are good and seems to be working. However, things I've noticed with PAR that I don't like:

1. First of it doesn't clean up itself afterwards. Which is nice in one way, however,
2. I'm not sure how or if it "caches". That is, when running the same file again, does it extract all again or check if already extracted? Can be a problem if script is modified and it runs the same extracted data... and not the new...
3. In memory is WAAY faster aswell, not cluttering up hd. Besides, you shouldn't really rely on that there must be hd space to be able of running some application. It's damn annoying to run out of space in general and if hd gets full while running some app, just because you are just running it is even more annoying.

perl2exe is quite nice too. But since that is commercial I don't like it that much. ;) Also, eventhough I doubt it, but if you "protect" your script using perl2exe, you never know if the creators of perl2exe can get your data.

Since I love doing stuff in Perl, and love the idea of one file, no installation hustle, PAR been nice, but your solution is better. Probably faster aswell. I do apps in perl, pack it and send it (and the reciever doesn't have to care about installing Perl and all modules needed for the script). With PAR it doesn't really feel good knowing it extracts "junk" that it never deletes. Sure, the standalone executable may be abit bigger, and not sharing files between other applications may seem like some waste of space, but in general I don't see how that can be too bad. Besides, having it all in one pack, you have all dependencies there and know that it works. A big plus is also that all files are packed in .zip and only extracted as needed (hopefully this means that same file isn't extracted twice!). Having it all in a .zip means even less space on hd. I'm jelous of programming languages like C/C++ in that way. But with your solution this is pretty close to that. Who cares that the binary may be abit faster than parsing and running scripts when most apps don't rely on pressing every clockcycle out of the CPU. With Perl you can archive your goals faster (and it doesn't have to be wierd, unreadable code) and you can concentrate more on the app in question.

I'm sure I've missed some other points about PAR and perl2exe that I discovered before, but I don't remember them atm.

YAAP could work although I prefer having a name that describes the module more... Hmm...

/ Ace

In reply to Re^15: problem with par as other user by Ace128
in thread problem with par as other user 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.