Why can pyhton deal with a big project?

[Cameron Laird]

In article <14430.40277.76485.132029 at weyr.cnri.reston.va.us>,
Fred L. Drake, Jr. <fdrake at acm.org> wrote:
			.
			.
			.
>  There's some namespace support, but I don't know how well-used it
>it.  My own thought on Perl is simply that it's hard to read, so
>others may (legitimately) say otherwise.
			.
			.
			.
As you know, people write endlessly on the virtues and vices
of languages other people use.  I'll add as little to that
volume as I can.

Perl has nice enough mechanisms that there are whole books
such as Damian Conway's valuable *Object-Oriented Perl*.  It
is absolutely possible for individuals to write Perl for big
projects.  The problem is that Perl so much observes its
TMTOWTDI mantra that it also seems easiest for individuals
to write stuff that only they can read--or, more to the point,
that is a poor fit for large-scale modularity and namespacing
in particular.

My own wildly speculative estimate is that under 1% of the
people who advertise themselves as Perl programmers use pack-
ages and namespaces "well".  That doesn't necessarily reflect
on the language, of course ...
-- 

Cameron Laird <claird at NeoSoft.com>
Business:  http://www.Phaseit.net
Personal:  http://starbase.neosoft.com/~claird/home.html