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

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
s/priceless experience/worthless experience/. Native Perl OO mostly ends up being about writing lots of repetitive useless code and forcing the programmer to deal with things that they should never even have to think about.

"Well, I don't think I'm crazy saying that using perl's implementation of OO is more stable and dependable then using Moose right now."
If you consider only bugs in Perl vs. bugs in Moose, you're probably right (although Moose is pretty solid). If you consider the number of bugs that you are likely to create, then Moose probably results in more solid code, especially once you start doing anything interesting.

In reply to Re^2: Modern vs postmodern? by hobbs
in thread Modern vs postmodern? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.