"Efficiency is a very relative term. Efficient compared to what? Runtime? Compiling? Deploying? Developing?"
Fair enough. Let me try to better articulate my intent, regarding that statment.
I meant with regard to actual deployment. As one simple example; I wouldn't use Perl to write something best suited for Client side JavaScript. Would you? ;-) But as you later stated; it really is fantastic for prototyping, and can indeed solve most real-world problems -- makes for a good problem solver; as I originally mentioned. ;-)
"Also, I assure you that you will make more money if you get hired doing Perl, than you will in almost any other language at this time (that said, you've got to be damned good and experienced)."Ahem... Didn't I pretty much say just that, in my reply? ;-)
Evil is good, for without it, Good would have no value
¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH
-
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.
|