If I can plug a fellow NC State grad (who probably posts here -- if you're here John speak up), NCSU didn't have a Perl course, and an undergrad (heck, a sophomore!) stepped up with his elite Perl skills and they let him teach a 1 credit hour class. Great stuff. I see Perl mostly mocked from OO folks, so reminding them that Perl has OO and showing them to CPAN may help. I also remember to bring up the phrases "ultimate glue language" and "swiss army chainsaw" as much as possible. Mentioning XS bindings, Inline::C, LWP, and the robot classes can't hurt either. Let them know all the things that Perl can do that their favorite language can't do in a non-trivial away. I think the academics who like Lisp and other functional languages would be happy with Perl. It's the OO types that need work. Perl proves styles can be mixed -- it's sort of post-modern mixed-media voodoo, and yep, that's threatening to a professor or student unwilling to take the leap and throw away preconceptions.

I don't think Perl needs to become "a better language" by any means. Perl6 will help the OO model, true, but it's rock solid as a language now. Java isn't in Universities due to corporations -- when NCSU switched, Java didn't have huge industry acceptance and app servers weren't that common -- it made a good *teaching* language, because it enforced OO principles and eliminated pointer-manipulation that a lot of weaker students couldn't handle. Perl isn't a good teaching language, hence at the undergrad level, it might be mocked. However, talk with your AI professor about functional concepts and more abstract stuff, and I bet he would be more willing to tolerate Perl than your data structures or CS1/CS2 professors. Also your Operating Systems folks will probably appreciate it since it can fork and manipulate pipes, etc -- just like C. There is a rigid part of university education that enforces OO dogma -- some of it is right, some of it is not -- it is your job to filter it out and extract what you can -- but what is taught to you is not neccessarily gospel.

In reply to Re: Re: Stereotypes about perl by flyingmoose
in thread Stereotypes about perl by nherdboi

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.