You seem to have the strange notion that Perl is only used for web development. I've use Perl, professionally, almost on a daily basis since 1995. But my current job is the first gig I've had where having Perl skills were mandatory to land the job. Remember, there's more to IT than being a webmonkey.
What about the guy that's trying to convince his dipshit manager that perl is the way to go? His manager would look at this site and probably not take it very seriously.
Yeah, really. The first thing a "dipshit manager" is going to do is look up perlmonks, and dismiss a language based on the appearance.
I like the idea of making it look more how the perl.org site looks.
I guess "dipshit manager"s never look at perl.org, but only look at perlmonks. Because, it used to be that perl.org looked "like 1995 all over again" as well. Now, after its makeover, there wasn't a sudden influx of "dipshit manager"s going for Perl instead of PHP because of the shiny new looks of perl.org.
What evidence do you have that indicates that "1995-ish" appearance of perlmonks is bad for perl, which also explains the new look of perl.org (and perl.com) didn't change anything?
-
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.
|
