The distinguishing twist could be especially helpful not only for an individual blog, but for Perl's public image as a whole. Any blog full of projects that are not web-based, simply wrapping some shell utilities written in C, or used to munge text files on a Unix system will help promote Perl as the general purpose language that it is.
Obviously, nobody wants to ignore Perl's strengths with text, for quickly whipping together small projects, and as a glue language. I'm not saying anyone should ignore those. It's important, though, that problems are solved which do more than just the perceived pigeonholes of Perl. Getting word out about those projects is what Perl's image really needs. BioPerl, any sorts of graphics work, audio, video, any graphical applications with slick wx, QT, or gtk+ interfaces, large systems, and projects that are already broadly visible which happen to be written in Perl or partly in Perl should really help break out of the pigeonholes.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||