Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I subscribed to TPJ one issue before they went kaput a while back. Then that was replaced by a subscription to sysadmin magazine... sort of -- I think I got 3 issues, but no big deal because I already had a subscription to sysadmin at work, and then I got the joyous load of crap 'tpj' tacked onto the end of sysadmin for a few issues. 3 articles at the end of some other magazine is _not_ the TPJ I had grown to love.

    So now I'm supposed to shell out $12 for another year? I probably will, but would like to see
    • Pros:
      • Professional attractive layout and very good production values. It's one of the nicest PDF's newsletters I've ever seen. Borrow your friends color duplex printer to do it justice.
      • Interesting content. I agree with the previous poster that brian d foy's article on "Better Documentation Through Testing" was the most interesting of the bunch.
      • Mostly free of advertising. I'm guessing that the TPJ folks would probably not find this to be a feature, but I've never gotten much out of the ads personally.

      Cons:

      • Short articles. The articles should have been a bit longer and more filled out. The code walk throughs were nearly missing or relatively light for most of the articles.
      • Only four articles. A third of the 27 pages were the same source code being printed twice. The volume of real content will need to double before I feel like it's worth all the grief we've been through with SysAdmin.

      TPJ is a big legacy to live up to and the new crew seems to be well on their way to reviving that bright light in our Perliverse. I'm mostly reassured.

      • More cons:

        • Icky typography. Spefically, the "fi" ligatures and "smart" quotes in inline code samples and boxes (though listings appear to be fine, for some reason).

        This kind of thing is a pet peeve of mine (the German version of PC Magazine gets this wrong all the time as well) -- please, people, if you're going to publish a journal that contains code, get an editor (or whoever is responsible for making sure things look right) who will ensure that code samples contain no ligatures, no "smart" quotes (unl

        --

        -- 
        Esli epei eto cumprenan, shris soa Sfaha.
        Aettot ibrec epesecoth, spakhea scrifeteis.