The worst thing about POE is their website. It's very bland. Sometimes I feel like yelling when I think about how terrible Perl programmers can be when it comes to web design. I will not point anyone by name, but you know who you are! Just google for gogopuffs and you will see what I mean. Thankfully, after far too many years, perl.apache.org and perl.org have new looks. Gee, guys ya think that was a good idea? Many of the younger generation like thinking of their languages as stylish and Perl does not put forth such an image at all. Just look at java.com, java.net or even php.net. Now I know someone will call me a troll and say "Perl is about getting the job done, not style or image. Perl is not pretty, it just gets the job done . . . blah, blah". Well, you can get the job done AND look good too. Personally, and I know that this statement will seem imflamatory, I believe that Perl attracts a lot of system administrators and in my experience, there is no other group on the planet that is worse at web design than system admins. This is just my opinion. Please let's not argue.
-
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.
|
