Follow Slashdot blog updates by subscribing to our blog RSS feed

 


Forgot your password?
Close
typodupeerror
×
Perl Programming

RIP: The Perl Journal 111

Posted by chrisd from the tpj-was-good-for-perl dept.
mbadolato writes "I'm surprised this hasn't been reported yet. Over at use.perl they're reporting that when the current issue of SysAdmin comes out, this will be the last installment of The Perl Journal. It's a shame. TPJ originally was stopped as a stand-alone, but was then included into Sysadmin. Now that's going too. We all owe a big thanks to all the contributers, and to Jon Orwant, for providing us a great resource in TPJ over the years."
This discussion has been archived. No new comments can be posted.

RIP: The Perl Journal More

RIP: The Perl Journal

Comments Filter:

  • We don't need perl (Score:1, Funny)

    by Anonymous Coward
    now we have .NET
    All our journals are belong to Bill
  • I have not followed the magazine a lot, but I remember reading it back in 1996, or maybe 1997. Back then, I got the impression that there was some ( a lot ) volunteer effort behind it back then. Could they, like, open source it - and maybe minimize the financial risk involved to it, I understood that they have been making some losses because of it. They could eZine it, and see if it could fly again. Costs would be minimal, or zero to them, just giving out the brand, basicly. It's a shame if a classic like this just disappears.

    • Re:Request it back to the community? (Score:5, Interesting)

      by jukal ( 523582 ) on Monday August 19, 2002 @04:01AM (#4096366) Journal
      this comp.lang.perl.misc posting [google.com] by Jon Orwant who started the magazine together with Tom Christiansen in 1996, gives some insight how the dilemma started. This is just a short clip:

      "there's no shortage of content out there, and the magazine could easily go bimonthly and then monthly -- indeed, when EarthWeb acquired TPJ I had thought that was the plan.".

      Apparently, TPJ was just in wrong place at wrong time, and fall to a vacuum because of that.

    • Strange as it might seem to me I still like paper copies of magazines which I can read away from my monitor... and unfortuantly most eZine's even those with PDF's don't tend to be very well formated in terms of layout etc for hardcopy.

      • > Strange as it might seem to me I still like paper copies of magazines which I can read away from my monitor

        I agree. However, it would not need to be only an eZine, they could also sell some company the rights to print it, and take just some percent of the possible profits. What could they loose? :)

    • They could eZine it, and see if it could fly again. Costs would be minimal, or zero to them

      Lets see if that flys shall we. Costs for an eZine.

      1) Hosting, dependent on load, lets say a basic package with minimal bandwidth $100pm

      2) Time, upload, updated editing, Content Management, configuration. Lets say 4 days a month, effective cost of $200 a day. Sure people can help out, but it still hits the daily job

      So we are already running at nearly a $1,000pm and we haven't even started trying. Bandwidth requirements goes up (a slashdotting a month should do it) and suddenly you are shelling out over 20k a year.

      e != free, haven't we all seen enough .coms implode to know that ?
      • > 1) Hosting, dependent on load, lets say a basic package with minimal bandwidth $100pm

        Hosting, dependant on load (if load < insane) zero. Get a sponsor. There's still a lot of companies that want the attention of Perl users.

        > 2) Time, upload, updated editing, Content Management, configuration. Lets say 4 days a month, effective cost of $200 a day. Sure people can help out, but it still hits the daily job

        I agree on this cost.

        > So we are already running at nearly a $1,000pm and we haven't even started trying

        Let's assume the cost would be that $1000 per month. Now, you got an eZine, and the brand of Linux Journal. You give printing permissions for a 3rd party, who sells paper-print copies of it and gives 5% of revenues to you. Can you cover the costs? I don't know, but I don't think it's fantasy economics either.

        • > and the brand of Linux Journal....

          Eeek. I was looking at that magazine on my desk. I meant Perl Journal ofcourse. I know, I am going to be flamed for this :))

  • The Perl Review (Score:5, Informative)

    by mir ( 106753 ) <mirod@xmltwig.com> on Monday August 19, 2002 @03:48AM (#4096332) Homepage

    The Perl Review [theperlreview.com] is exactly what you describe: a Perl journal, distributed only as PDF at the moment. The publishers hope to get it on paper one day, but they wanted to get it started., so the first 5 issues [theperlreview.com] are already available.

  • Sad News (Score:2, Interesting)

    by jamieo ( 22197 )
    This is really sad. I've subscribed to TPJ since about issue 3 and have all the issues. The SysAdmin deal was welcome, but only to keep it alive.

    TPJ was such a valuable resource for me as a perl hacker. You learned so much from each issue and people always contributed interesting articles.

    Seems like my 2 year subscription will now be for SysAdmin - something that I'm not really interested in :(
  • Perl is the expression of a comunity so an eletronic form with daily news/articles/forums it's more appropriate; of course you can't put a eZine on the tea table, showing your hosts that you're really involved on the tech thing, but that's are luxuries not real needs.
    • burn sulpher bearing coal that you have to knock down a lot of trees to get to and make yourself more dependent on foreign oil.

      Blimey, this redistribution of wealth is trickier than I thought -Dennis Moore

      KFG

  • Periodicals are advertising supported... (Score:2, Insightful)

    by Anonymous Coward
    ...and advertising revenue is directly proportional to the receptiveness of the target audience. An audience more impressed by colors and pictures - in other words, less so than by actual information - means more total advertising revenue, and more available revenue means more players in the market.

    This is why you don't see many print periodicals for serious work tools (*BSD, Perl, GCC) and you see mountains of them for toys (Windows, .NET, Visual Basic).

    This isn't sad news. It simply means that the Perl community's priorities are where they belong.

    • Advertising revenue is directly proportional to the audience of the magazine and its demographic makeup. A distant third, barely visible on the horizon, is the audience's perceived receptiveness to advertising.

      You mention that there are mountains of magazines for "toys" such as Windows, .Net, and VB, and insinuate that that's because people there like ooh pretty shiny things over content. I counterclaim that a) it's because the audience for such magazines is vastly larger than that for *BSD, Perl, or GCC, leading to far more advertising revenue than is possible for a magazine centered on any of the latter three things, and b) the size of the audience is in large part determined by how little most people are willing to pay for documentation about Open Source software. "I can always just read the man pages or check Google and Google Groups. Why would I pay for a print magazine?"

      To top it off, what advertisers are going to be buying ad space in your hypothetical GCC magazine? "Richard Stallman, live and uncensored, on the hot new tape, When Gurus Go Wild!"

      It's not about content versus pretty pictures; it's about audience size and how much of that audience is willing to pay for things.

      • Pay for things? but I want it all for free/Free!
        and somehow, I want to make money for doing it for free/Free.
      • It's not about content versus pretty pictures; it's about audience size and how much of that audience is willing to pay for things.

        I still agree with the parent post. Most technical print magazines have very little useful content. The only reasons I keep a magazine subscription going is to know what the buzzwords-of-the-month are and to see what the hot-products-of-the-month are. In this respect, the advertisements are actually the content.

        Quite honestly, if I were to take the things I see in a magazine seriously, I would have a record number of failed projects that no one else can maintain to claim responsibility for. The fact is, if a magazine publishes something as a bold-faced headline, odds are that technology is so immature or vaporous that it will disappear into obscurity before I even understand what it is. This is true for nearly any technology domain, regardless of which company is backing the brand names and acronyms.

        Conclusion: magazines are good for buzzwords and "the bleeding edge", but look elsewhere for things on which one can risk a reputation.

        • I still agree with the parent post. Most technical print magazines have very little useful content. The only reasons I keep a magazine subscription going is to know what the buzzwords-of-the-month are and to see what the hot-products-of-the-month are. In this respect, the advertisements are actually the content.

          I'll certainly agree that magazines often have very little useful content. But that wasn't what the parent post was arguing. It was arguing that what drives up advertising revenue is having an audience receptive to buying stuff, and that that was linked to liking pictures over content. That's not what drives advertising revenue: it's audience size and audience demographic. The value of the content has less to do with that, beyond its value in attracting new readers.

          I just don't see a large market for most any Open Source magazine beyond the broad ones like Linux Magazine. One for GCC, as the parent poster suggested, wouldn't fly, and not because it would be more content than other tech magazines.

    • ...and advertising revenue is directly proportional to the receptiveness of the target audience. An audience more impressed by colors and pictures - in other words, less so than by actual information - means more total advertising revenue, and more available revenue means more players in the market.

      Easy solution, Post naked pictures of CowBoy Neal, the slashdot crowd would all buy one, thats a million copies right there! ;)

      Hehe, seriously, I enjoyed the TPJ also, but i only play with perl, I dont do it for a living. I enjoyed the articles for the learning experience. In fact, I read the changelogs for gcc/perl/bsd/linux just to see what is "Really" going on, thats what I like about slashdot and freshmeat, to announce new releases.



  • With Perl Journal gone, what will replace it ?!

    I hope not ".Net Journal".

    • I'd really like to see a magazine that covers all of opensource programming. Perl, Python, PHP, MySQL, GCC, bash scripting, opensource libraries, opensource tools, free codecs, etc. Everything a programmer that develops opensource software or with opensource software could want and no commercial crap we don't want. Something like Dr. Dobbs but covering only opensource.

      If it covers more topics it'll have a wider audience which in turn will give it more advertisers. SysAdmin is a good magazine but it really isn't programmer-centric or 100% opensource so there probably is room for another magazine out there.

  • The Perl Journal story .. in Perl! (Score:5, Funny)

    by wackybrit ( 321117 ) on Monday August 19, 2002 @05:51AM (#4096544) Homepage Journal

    First the money went..

    $tpj =~ s/\$//g;

    So two magazines merged..

    $sysadmin .= $tpj;

    The advertising slump hit hard..

    $sysadmin =~ s/ActiveState/Make Money Fast!/g;

    And eventually they lost money merged together too.

    $sysadmin =~ s/\$//g;

    The arse totally fell out of the operation.

    $sysadmin =~ s/.//g;

    So they shut up shop.

    exit;

  • IOPCC? (Score:3, Interesting)

    by GMontag451 ( 230904 ) on Monday August 19, 2002 @06:09AM (#4096577) Homepage
    So does this mean that the IOPCC (International Obfuscated Perl Code Contest) is defunct? Reading the winners from that and trying to figure out what they do was something I always looked forward to each year.
    • (* So does this mean that the IOPCC {International Obfuscated Perl Code Contest} is defunct? Reading the winners from that and trying to figure out what they do was something I always looked forward to each year. *)

      That reinforces my theory that Perl fans *like* obfuscated code. If something is too easy to read, then Perl fans get bored.

      Nothing wrong with that. Everybody's boat floats on different water.

  • Perhaps... (Score:4, Insightful)

    by ldopa1 ( 465624 ) on Monday August 19, 2002 @06:32AM (#4096616) Homepage Journal
    Perhaps the reason that nobody has reported it is that very few people read it in the first place, and as such, very few people care.

    This may also be the reason that they aren't going to be continuing with the journal in the first place, don't you think?

    I doubt few people lamented the end of the Ultrix journal....
    • Indeed, far more people will read of the passing of TPJ than ever subscribed to it. At the end of the year 2001, The Perl Journal had a circulation of 16,000 including newsstands.
    • Thank you for pointing out what so many folks seem to have missed: the thing is dying because it isn't popular.

      Of course, I'm still waiting for someone here to pull a Loki and insist that we all must dig into our pockets and make donations to keep it going even if we don't care about the stuff. It'll happen...
    • I had wondered for a long time where Perl Journal had vanished too. Perhaps that is also part of the problem -- if even Perl zealots don't know where to find the journal, what hope does it have?
    • I subscribed to TPJ back when it was TPJ. It used to be a nice journal until Sysadmin took over. They had clever/funny covers, good articles, and all was nice. Then it became pretty corporate feeling when Sysadmin was publishing it, with more advertisements than articles. The number of pages dropped, and the cool covers disappeared. It basically turned to shit, minus the occasional article from the oldtimers. That's why I don't care now. I *did* care that it was going under way back when, before Sysadmin started publishing it.

  • No Real Surprise (Score:3, Insightful)

    by elmegil ( 12001 ) on Monday August 19, 2002 @08:35AM (#4097066) Homepage Journal
    I think part of the problem is that Sysadmin did their best to offend the TPJ subscribers they inherited.

    • Content was somewhat redundant, with perl articles in the Sysadmin section as well as the TPJ section.
    • Only 3 or so real TPJ articles every other issue (at least it seemed pretty sparse) as opposed to the 8 or more in the old TPJ.
    • Most damning, if Sysadmin treated everyone like they did me.... As soon as the two merged I was inundated with snail-mail spam. Eventually I figured out that some code on the address meant it came from Sysadmin, and I called and complained. They told me I could opt out, why was this a problem? At least I got opted out and the flow had slowed way down since then.
    I had already renewed my subscription (boy do I regret that doubly now) but wasn't planning on renewing again anyway. Not because TPJ wasn't wanted, but because what I was getting in Sysadmin wasn't really TPJ any more, and Sysadmin itself isn't of any interest or use to me and they abused the relationship.
    • I never felt that SysAdmin was the right place for TPJ articles. The typical system administrator writes scripts to parse logfiles and such; he or she has no need for the envelope-pushing, clever techniques promoted by TPJ. TPJ was a wonderful journal with high standards for content and editing (and layout, back when it was a stand-alone publication). I miss it. Incidentally, I still like SysAdmin too.
  • I cancelled because 1) It costs too much... 2) Has few issues. 3) Has little content. 4) Has more advertising that content. 5) LinuxJournal doesn't have any of these flaws and Rocks!! To bad for Perl

  • O'Reilly to publish 'best of' anthologies (Score:5, Informative)

    by jacobito ( 95519 ) on Monday August 19, 2002 @10:37AM (#4097891) Homepage

    In case you haven't heard, O'Reilly will be compiling and publishing three anthologies of the best articles from the Perl Journal:

    Games, Diversions, and Perl Culture [amazon.com]
    Web, Graphics and Perl TK [amazon.com]
    Computer Science and Perl Programming [amazon.com]

    If you've never read TPJ before (or even if you have), be sure to grab one of these books when they come out. TPJ set a high standard of quality, with articles that were intelligent, entertaining, and usually a bit quirky.

  • but I first subscribed to TPJ about 18 months before its sale to EarthWeb. That sale seemed to be the beginning of the end. I loved TPJ and found that I often learned more from it than I did using either web pages or books. But obviously I must have been in the great minority. I'm still wondering why.

    It does make me wonder though if any print programming magazines are doing well these days?

    • I subscribed at issue #4 from Dr. Orwant himself (Usenix 1997), and I agree: the EarthWeb deal was the start of the downward spiral. I remember how EW wanted you to subscribe to their website (credit cards only, thanks), and they would throw the print version at no additional charge... I would still send my money in the old fashioned way. I suppose TPJ is yet another victim of the dot-com-bustables and the down ad market.
  • I buy SysAdmin at shops because the mail delivery here is atrocious; I've tried subscribing to magazines in the past and it never has worked. I was annoyed at the diminishing page count in SysAdmin. The Perl Journal and Elizabeth Zinkann's book review column were the main reasons I continued buying it. They dumped the latter at the beginning of the year and now they're removing the remaining reason. I'll still browse it and buy a copy now and then if it has a really superior article on some topic I consider vital but I'm no longer compelled to complete the set.

Slashdot Top Deals

Keep up the good work! But please don't ask me to help.

Close