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
use Perl Log In
acme (189)
acme
(email not shown publicly)
http://www.astray.com/
Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.
(email not shown publicly)
http://www.astray.com/
Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.
Wednesday July 26, 2006
09:57 AM
Please do it
I've been hearing a lot of talk recently about how people are looking forward to doing something for $random_technology_which_isn't_finished yet, but they'll hold off until it is finished. Here's a tip: you can do it now, and without that technology. Don't wait for new technology. Don't wait for new software. Real something is always worth more than potential something. Please do it now instead!
Please do it
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
It comes from experience and lack of time (Score:1)
It comes from code that sorta works, that is going to never get beyond sorta works.
It comes from knowing in advance you are going to have to submit 20 or 30 bug reports just to get the thing somewhat usable, and not having the time to invest in it right now, because you are writing 20 or 30 bugs for some other thi