Give it a try - you'll like it.

…Maybe. But I am skeptical of everything Google does. I’m finding AngularJS a very hard pill to swallow, for example, though I'm fighting to get into it because it seems a good career move. A toxic position, really. Doing something you dislike for money. I wrote a micro-wiki platform to replace my personal Kwiki stuff two weekends ago in Catalyst and a possible Catalyst replacement in pure Plack:: the next week because as much as I like Cat, it has a lot of things that bother me. I'd much rather be doing that and even Mojo and Dancer2 or Amon2 for that matter than Angular or Go. If I have to do something else, it'll be modern ECMAScript.

I more or less hate or at best tolerate most programming languages besides Perl; I only enjoy JS because of the DOM and its general Perlicity. I was trained early on CS and fell away from it for 15 years or so because it was so unappealing to me. Perl is the only reason I came back; the only reason I'm a professional programmer.

I'd love to see Go calling C inline like the Perl and in 27 lines of self-compiling code. :P Also, PDL is a well known, "real world," Perl module for number problems and it's twice as fast as Go here. I would have reached for it myself if the 90 seconds of code I wrote at first didn't satisfy a performance issue in an app.

Perl is knocked overly often and often by putative fans who play apologist… "Shucks, Perl is fine except it sucks." Perl is frequently not just a terrific choice, but the best choice; dev time, speed, reliability, etc. It's time we spoke more plainly about that. If Perl had the reputation it deserves instead of the reputation its competitors have heaped on it, I probably wouldn't be worried about needing to learn Angular right now. :P


In reply to Re^6: Camel vs. Gopher by Your Mother
in thread Camel vs. Gopher by reisinge

Title:
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, details, 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, summary, 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.