Agreed. There's a certain patina of content-free writing in it. However, I've been around that style of writing so long that I view it to be the 'language' of the types of readers eWeek is interested in. Poised in that style it's likely to be more believable to those readers.

Plus, the Perl coverage was so scant I hesitated in bringing it to PM, yet it was there, even though it ignored Perl's history as one of the oldest and most used Open Source tools ever. Shortsighted on their part, but still useful for us nonetheless IMHO.

The mention of Perl only with web development tools still makes me shudder.

Ultimately, it was good to see so much page space devoted to the Open Source category and helping to better legitimize it, even though much of it was from 50,000 feet.

---

---

• 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.