As you can see from many of my other posts on similar topics, revdiablo, I am a firm believer in the need to understand the entire system you program for. The particular syntax and tool set of Perl is of minimal importance in this bigger picture, though its flexibility certainly helps.

In my own case, my programming has been vastly simpler _because_ I understand my systems just a bit better than the average brawn. Perl is an excellent tool in my toolbox, and I give it credit for making some tough problems solvable.

Having a stable, predictable OS under your box's hood is crucial to success in a commercial enterprise. The OP was looking to do some of the same kind of things I've tackled, so I think my input was quite valid.

Feel free to downvote; that is your right and your responsibility. I've rarely been a politically correct beastie, and I'm unlikely to start now. The world is full of people who want their neat little boxes unbent; that's one of its major problems, and crying 'netiquette foul' when I was specifically answering the question borders on that, IMNSHO, though, as I say, your stripes earn you the right to opine however you please.

The OP is coming from COBOL, one of the most insular programming systems ever developed. Given that he was talking about nuances of system calls, I suspect that he has visions of apps that push Perl around corners that go a little bit further than CGI.pm intended. It is true that _learning_ Perl can be done on any scriptkiddie car that will run it, but deploying a Perl app successfully in a commercial environment demands stability, consistency, and predictability. When I have direct commercial success in such an endeavor, and FreeBSD has cushioned my @ss in doing so, should I not spread the word? And, yes, in a prior incarnation I was paid to proseletyze for BSD, but this success has come long after that time. I salute the people who specialize in Perl education and Perl usage, but I am not one of them. I will also freely admit that I can't hold a candle to most of the Saints here, including yourself, in the usage of raw Perl itself. When I as a pretty successful generalist sees a place to contribute something of value, I will do so. I would hope that the initial lines of my post were enough to establish that I expected my post to be taken as personal opinion. I do hope the OP finds it valuable, which was my intention.

In reply to Re^3: Effect of OS Platform choice for learning and doing Perl well by samizdat
in thread Effect of OS Platform choice for learning and doing Perl well 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.