comment on

It's causing more damage than benefit

IYHO, of course. Personally speaking I see it as neither a huge boon nor a terrible disaster.

and fixing old code is easy

It really isn't. Technical debt is a huge problem within the industry - just ask any COBOL programmer (if they will let you onto their superyacht). I have seen comments like

# This next line is essential for this subroutine to work but I don't 
+know why.
# DO NOT TOUCH OR REMOVE IT!
[download]

too many times to be shocked or surprised. Any time you touch old code you risk breakage and the older the code the higher the risk.

The more logical Perl is constructed, the easier it is to promote.

Completely agree (so long as it doesn't end up just being a dialect of python ;-p)

🦛

In reply to Re^5: sort AoH buggy? (deprecation candidate) by hippo
in thread sort AoH buggy? by LanX

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.


laziness, impatience, and hubris
	PerlMonks