Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

Comment on

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

“Downvoted” though my comments were ... I at least did not lurk behind “Anonymous Monk” to say them.   (heh ...)

Will, the root problem of your “grand pronouncement,” just like every graduate-student (or senior undergrad) who has “created a New Programming Language, accompanied by A Paper Extolling Its Superiority to Everything That Has Come Before,™” is simply that this really isn’t a terribly useful thing to have done.   Let me explain.

“An implementation of the Perl-5 programming language,” on my present machine, “sub-optimal” though it may be, occupies all of about 86 kilobytes of object-code.   On the other hand, the CPAN library of the system is about 96 megabytes.   And the client project library, as previously mentioned, is more than a million lines of custom-written code which in fact cost well more than a million US Dollars to produce.   This situation is hardly atypical.

Therefore ... in light of this, how fare your “commandments?”   Frank answer:   “not so good.”   Because they not only “demand” that I change, but “require” me to change ... and to reap what “benefits,” exactly?   Just in order to “Soak In The Goodness™ Of” whatever you have done.   Is this a cost that I can justify?   No, it isn’t.  

Plan Accordingly.™

Sure, “new code” is being written all the time, and so all of us are always clamoring for improvements.   But none of us can afford to de-stabilize, let alone change, “what has been done before.”   And this is very much what has made some of the truly-innovative “hacks,” like Moose, be so successful and widely-accepted.   It was “a significant improvement” that you could take advantage of with relatively low business risk. It’s not simply that you can use Moose;.   It’s every bit as much, if not much-more, that you can also say:   no Moose;.   You can mix the old with the new.

In reply to Re: Perl 5 Optimizing Compiler, Part 9: & The Low-Magic Perl Commandments by sundialsvc4
in thread Perl 5 Optimizing Compiler, Part 9: & The Low-Magic Perl Commandments by Will_the_Chill

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 all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others making s'mores by the fire in the courtyard of the Monastery: (5)
    As of 2018-03-17 14:47 GMT
    Find Nodes?
      Voting Booth?
      When I think of a mole I think of:

      Results (224 votes). Check out past polls.