Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

They might have legitimate reasons for changing (the normal one being that they have a programmer on staff who knows some other language, and they don't have the time to maintain additional code ... of course, if that were the case, they wouldn't have time to re-write additional code, either).

Other legitimate reasons include wanting something compiled so that people can't as easily inspect the code, if it's something to be sold as a product, or to reduce complexity if the program has to interface with some other system that only provides language-specific APIs. There may also be issues with needing to reduce the execution time, memory footprint, or some other metric and they want to go to a compiled language for that.


Anyway, my typical issue is that if the code currently works correctly, there is the possibility of it not working correctly after the change. If they don't need to rewrite the script, it may be enough to have to documented to the state where someone else with only basic understanding of Perl can take over.

This is an initial savings to the company, as they don't invest more time to get to the same level of quality that they currently have. It can also reduce risk, as an incorrectly translated program may have defects in it ... depending on the project, that may not be acceptable (but if that was the case, they'd likely have better documentation).

One of the problems that I've run into, even staying within the same language, is that often the complexity is there for a reason -- handling edge cases, etc, and an attempt to rewrite the code might remove all of the embedded knowledge that the code contains.

In reply to Re: How to retain perl in-house code by jhourcle
in thread How to retain perl in-house code by basicdez

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others chilling in the Monastery: (4)
    As of 2020-12-01 04:42 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found