http://qs1969.pair.com?node_id=1216517


in reply to Re^2: Is it still worth learning Perl as a first language?
in thread Is it still worth learning Perl as a first language?

I had my response to the topic right from the start. But wanted to read the others here before my reply. So as not to simply parrot anyone. Now at the end of the list. I (not surprisingly) see YM's ties in quite nicely. So I'll reply here. :-)

Definitely choose Perl, and learn it well. Especially if it's a language you like. If you've learned Perl; C, and JavaScript are already in the passenger seat. So you're effectively (reasonably) comfortable in 2 additional languages.

You can use Perl(tm) as a solution to almost any problem. The same cannot be said of most other languages. Granted, Perl may not be the most efficient solution. But businesses are always looking for solutions, and if you have a solution, you have a job. Well, you're at least that much closer to having a job. :-)

Again, if you like writing, and working in Perl. You should really try to learn it well. Who doesn't want job doing something they love?

I'd rather make less money doing something I love, than making more money, doing something I hate -- which is not to say you'll make less money working in Perl. In fact if you know it well, quite the opposite is probable.

tl;dr;
Perl adds value. Learn it. :-)

λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

  • Comment on Re^3: Is it still worth learning Perl as a first language?

Replies are listed 'Best First'.
Re^4: Is it still worth learning Perl as a first language?
by stevieb (Canon) on Jun 13, 2018 at 19:54 UTC

    Your response here is fine (++), but I have just one comment:

    "Perl may not be the most efficient solution..."

    Efficiency is a very relative term. Efficient compared to what? Runtime? Compiling? Deploying? Developing?

    I've been coding Perl since ~2001, and I assure you that unless you're doing Real Time type work (such as microcontroller business), Perl is pretty well efficient enough for almost all tasks, given enough CPU and memory (I'm speaking runtime here). When I code in C/C++ for a microcontroller, I almost always prototype in Perl first to get my ground ready, then do the lower level work. I can deploy anything in Perl (including 100% test coverage and full documentation), quicker than I could code, build and test anything in any other language, so there's that ;)

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

      "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

        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?"

        No, but that wasn't part of your OP. Why not ask that straight up?

        Joke around homeboy, ask rhetorical questions. I love you, will always be here for you in your desperate need for attention, and will code circles in 10 languages around you to keep you content.

        Love,

        -stevieb