I hate these threaded replies, especially when there's alot, so I'll just respond to myself again and hope people read this. There were a few comments like "New languages, like Ruby, Python, PHP, and Ponie are going to be on the rise in terms of living-ness." I brought that up in CB before I started this thread. I figured that Python usage won't continue to increase at that rate (assuming my stats indicate usage rates). I made no claims about how well my stats indicate usage rates. They're simply something to consider. How popular a language is and will become should be a consideration in which language to use, especially when there's a ton of modules that you would like to continue to be maintained.

I guess I'll get off-topic again to answer some of the other off-topic posts. I use a programming style that works for me. I could handle it. For my past scripts, I haven't used strict, I used all globals, etc. I believe that the structure of my large script, and the comments I used, might actually make it easier to follow than a comparable script that uses strict and scoping, etc. I've given examples of the difficulty that I've avoided by using my style. I could handle my style just fine, nobody but me will be maintaining it, there seem to be fewer bugs, if any, than in the average script, and continued, harsh criticism of my style (mostly in other threads) when it's off-topic is not appropriate.

I offered snippets of my major script to the public for what they were worth. When someone told me that he didn't know what one of my scripts would be useful for, I repeated how I'm using it. I never argued that it would be useful to others because it's hard to tell, and the best way of asking is sometimes to post an already completed script.

Another script made a simple, user-defined list of variables that aren't set in modules and also provided a safe version of Perl's reset function. Overall, the responses I got to it were insane.

An occasional style critique is acceptable, but what I got wasn't. All my responses were appropriate. Be specific when you raise those past issues in a new thread, and I'll be more specific too.

In reply to Re: Fearing the demise of Perl by Wassercrats
in thread Fearing the demise of Perl by Wassercrats

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.