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.

Leaving use.perl 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Obviously I can't speak for everyone who has non-use.perl blogs, but I can explain why I've set mine up.

    I'm not leaving use.perl. I'll still be posting a lot of stuff here (or, at least, that's the plan). It's just there is stuff that I'd like people who aren't part of the Perl community to see as well and asking them to come here seems a bit strange to me. Like a party where two different groups of people don't mix.

    I'll see how it goes for a while. Maybe I will get a lot less comments. Maybe I'll find th

    • As someone who posts fairly rarely to his general blog and even more rarely on use.perl.org, I'm with Dave here. I made a decision last July or so to only post Perl stuff here, and there's not that much I've done since that I think is of interest.

      Other people evidently feel that the word 'journal' is more important than the word 'perl'. Fair enough.

      Perhaps what's missing in the wider world of blogs like aevil's, davorg's, ask's, boojum's and my own is the 'Friends' interface and the interconnectedness of the comments interfaces. But the software is getting there for that; I can get rdf [ician.co.uk] of what's recently been updated on Dave's site and he doesn't have to lift a finger. MT has comments enabled by default. With not much time and effort, you could tie things together again even over sites.

      I think I've wittered enough for now. But I've got Bad Ideas going now.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.