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.
What cultural values do we have? (Score:1)
The Perl community hated him. For years afterwards his name has been vilified. We've complained horribly about the bad impression he gave Perl. We still complain about that.
Why? Because Matt Wright didn't understand security. He didn't design his code for reuse. He didn't follow basic best practices. And many beginning programmers used him as a model for how they should program. Every one of those criticisms is valid.
Now go look at some of those PHP applications out there. Examine them. You'll find that Matt Wright's spirit lives on in PHP, in spades. Similarly look at how Rails handles databases. If you care about database design, that's not the way to do it.
Then go read Worse is Better [dreamsongs.com] and see the parallels. Characteristics which make software worse from one perspective often make it better from another. In particular maintaining programming ideals around areas like security, good design, code reuse and the like often get in the way of making software that will become popular.
What are our values? How much are we willing to bend in the name of popularity?
Reply to This
Re: (Score:2)
Re: (Score:1)
That said, we've gone a long ways towards making things simpler. Just compare how difficult it is to get a Perl library installed versus installing a useful Java library. We can make it simpler still, but Perl already has a pretty good story to tell.
However it is never going to be as simple as a single file install. It just ain't going to happen unless