I blinked at the use of 'legacy' and 'perl' in the same phrase, as I'm used to thinking of perl as a relatively new language, but a quick mental inventory of our network made me realize that we in fact run legacy code as well -- but only because it is still doing what it was originally designed to do, not because it's unmaintainable. The bits that have needed to change over the years, have.
A question that came to mind while reading this post: does anyone have a grasp on how many active perl programmers are out there, versus the number of active java programmers? (I mean folks who code on a regular basis and have progressed farther than 'Learn to program X in 21 days' level.) A factor in deciding which language management should put their energies behind would be the size of the pool of programmers available for the task, from the standpoint of both cost (higher supply generally lowers the price) and community resources.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
