I have seen a lot in this thread, and indeed in general talk, about how perl should be extended, or managed, in order to make it a panacea for all that needs to be programmed.

Don't get me wrong... but all languages have their unique niche.

I love perl, perl is a GREAT language for the things that I do with it... but it's not the right programming language for every situation.

Perl stands for Practical Extraction and Report Language... not Perfectly Everything's Replacement Language, for every other language and system on the planet.

Yes, improve, work, make perl WONDERFUL! Just don't make it impossible and useless. You can only change it so much before losing sight of the fact that it is GREAT for certain things.

I still think that in certain situations, it is better to embrace the fact that a different language should be used, rather than forcing a nice square peg like perl, that fits wonderfully into nice square holes, into a round one.

This will just make the people who had THAT experience with perl as their first real experience not want to embrace it like we have.

Whatever you do with perl, whatever solution you come up with... make sure that it is the BEST solution to the problem that you can thing of. If you think that lisp is the solution to the problem, and you can code it in 20 lines in lisp, why make an issue of it and vow to use perl in this project. Instead, take what you have learned from the experience, and if it seems practical to extend perl to make such endevours practical under it, then come back, and give this back to perl.

This is the way that we make the language that we love the language that everybody loves, rather than the language that is cryptic and painful to learn.

Just Another Perl Backpacker

In reply to Perl's Niche by Nitsuj
in thread why i may have to leave perl... by eduardo

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.