Perl is an artistic language. It is jazz, where formal rules are pushed and cajoled into presenting the same thing in a new (maybe even better and more efficient) way.
Come on guys. Don't make the mistake of Apple in the 80's, or IBM in the 90's (re: OS/2). Principles are fine, but should they stand in the way of the betterment of Perl, and the IT world?
When I hire a contractor to build a deck or a new staircase, I damn well want to see his certification and experience. "Let the results speak for themselves" just won't cut it when my child has fallen through the staircase because I hired someone who spoke more than I knew. The same goes for airlines - would you want to fly in a plane where the pilot hadn't gone through the most stringent of tests and exams?
Recall the first word in the acronym of the language we admire: "Practical"
- dharma
-
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.
|