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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
"Hated" ideas people? (Score:2)
I remember a couple of years ago falling into the "Replace POD to XML" camp, until tchrist set me straight. I've also been painfully aware whenever that argument resurfaces, along with a couple of other latent memes that circulate through the Perl community. Like replacing Perl's syntax with XML, so we don't have to worry about maintaining a parser anymore (duh!), or the more recent resurgent meme that Parrot is a folly and we should just use a Scheme VM for Perl6...
It's important to keep a beginner's mind here, otherwise we'd be a pretty boring and exceptionally stagnant development community. But a room full of beginner's minds generally won't get threading done right, fix the thread safety of regexes, integrate Unicode into the core or reintegrate EBCDIC. So we need both, and Perl6's release valve offers a way for the two groups to coexist more peacefully than before.
Reply to This
Replace Parrot with a scheme engine? (Score:1)
Plenty of scepticism about the whole Perl 6 enterprise, but I've not seen the 'use scheme' thing.
Re:Replace Parrot with a scheme engine? (Score:2)