Just in case there IS a larger issue that leads to a lawsuit

Your software license can mostly protect you from such issues. If you sell proprietary software commercially, you may be on the hook. If you sell services and support for your Open Source licensed software but don't specifically sell the software itself, it's generally a nice ride ;)

I would hazard a guess that probably 50/60 of my CPAN distributions run under 5.8. A few require 5.10. There may be one or two that need 5.10+. IMHO it's not up to the developer to write software to force people to upgrade, it's my job to be as compatible as possible.

To me, it boggles the mind that someone would try to use a Perl version that has been unsupported, insecure and end-on-life for a decade now. What's next, running your companies website on an Windows NT server?

Trying to force upgrades is a fools errand. Policies, politics, infighting, nonsense, ego, money, you name it, you'll come across it. I was a sysadmin once, trying to advocate for compliance to no end (in the financial/gaming industry even). As we see over and over, companies just won't spend on upgrades until they've been exploited. Until you've done work for a billion dollar corporation where you get to see the problems from the inside, disgust and frustration as to the 'why' will be the case.

Write software for the lowest common denominator of users, while at the same time promoting why certain changes would be best. Just because my software will run on 5.8 doesn't mean it won't run on 5.38, and that's the real point here... one doesn't need to force an upgrade, one just needs to position their software in a way that facilitates one.

-stevieb

In reply to Re^4: Why causes Exception::Class a fat-packed perl application to fail (but works with 5.38) by stevieb
in thread Why causes Exception::Class a fat-packed perl application to fail (but works with 5.38) by Darkwing

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.