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.

use Perl

All the Perl that's Practical to Extract and Report

Perl 5 day summary More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Thanks! (Score:1)

by yDNA Barak (3336) <{andrew} {at} {sweger.net}> on 2005.09.10 13:23 (#43211) Homepage

Thanks for the summary. This is all good news to me. Despite the lack of action, it sounds like people understand what's needed. Further illustration of the connection between core developers and the tools companies use to make their money are needed. A simple marketing message that can be repeated ad nauseam.
Here in Seattle I'm pimping Damian's book. When one writes Perl as a profession, they should stick to the guidelines. There's still room for Perl-as-art, but we have a common foundation that's not difficult to agree on. The packaging and distribution are problems. But this is the right community to solve those problems.

--
The great thing about multitasking is that several things can go wrong at once.

Reply to This

Get More Comments

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