I mostly agree with you on your University comments. I am glad that my Computer Science study began with Pascal and from their went to C. The year after mine, Melbourne Uni Computer Science replaced Pascal with Miranda (a functional language) which I think is a capital idea - first teach students a less common (but powerful) approach before they get 'stuck' into procedural thinking so that they can see more than one way to do things.

Software Engineering courses these days contain higher level subjects these days like Web Engineering where concepts like online communities are discussed. The fastest way to play with online communities is certainly not C :) Courses like that are definately up for alternative approaches like Perl or OpenACS (as is used for that course).

FYI: I am based in Sydney myself these days, and your use of the term "enthusiast" is an important clarification. Developers or admins who know how to hack a short perl script are not the same as a Perl developer.

Another thing I should point out is that I also didn't use to consider myself a "Perl Developer" - candidates for hiring as a Perl developer can include people comfortable and experienced with good programming practises who have shown their adaptability to other languages. Unfortunately that skill is even harder to test than Perl skills!


In reply to Re^2: Popularity of Perl vs. availability of Perl developers by aufflick
in thread Popularity of Perl vs. availability of Perl developers by aufflick

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.