Perl has been ported to at least 60 (100+?) different operating systems, including (as mentioned above) PalmOS. In every case, the same basic functionality exists. (Obviously, if forking isn't supported on the OS, then you can't have fork work in Perl, and the like.)

As for requiring a dedicated server - it all depends on what you're doing. Perl itself is very fast, compared with VB. However, because you can do some really complex things in Perl very easily, it can be very ... dominating. Most commerical uses for Perl do require their own servers. Not because it's Perl, but because the application built in Perl has requirements. (Report servers, e-commerce apps, etc)

I would recommend doing at least one of the following steps:

  1. Download and install ActivePerl on your desktop. Play with it and get a feel for the requirements of what you're doing. In many cases on Windows, using WScript, JScript, and/or VBScript may be more appropriate.
  2. Talk to your manager. If you're asking the question, you probably have been asked to do something by your manager.
  3. Bring in a Perl consultant to discuss the issue. Sysadmins are trained to be very conservative. Remember, it might be your application that's causing the server to slowdown, but it's his job. (There are old sysadmins and bold sysadmins, but there are no old and bold sysadmins.)

Oh, it's not a Perl compiler - it's a Perl interpreter. Perl compilers are different beasts.

------
We are the carpenters and bricklayers of the Information Age.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.


In reply to Re: ISO technical document outlining system requirements for Perl by dragonchild
in thread ISO technical document outlining system requirements for Perl by xburrows

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.