All I, for one, have done from this discussion is start to browse around
and try and see what Perl must look like for the seeker, from the
outside. It comes down to perceptions I believe. 

Changing the general public perception is difficult in that it also
involves "training" the public of where to find a heartbeat. Take for
example a look at the article archive on perl.com:
http://perl.com/pub/q/Article_Archive

To the uninitiated or person "considering" Perl, seeing articles
averaging 5+ yrs of age, it looks like a ghost town. The reality is that
many of those articles are still relevant. But how can you explain/train
that concept? The parallel is people looking up at sourceforge and like
sites, ... to see a module that's 5 yrs old will communicate that it's
headed for death. Do we "bump" these articles or rally for writing new
ones? If they looked to CPAN to start with, they'd see a very active
bunch. The truth is our Perl world is very stable and we're all busy
getting work done by writing Perl code and we've stopped writing about
Perl. Newer alternatives are still in ramp-up stages, and so the
articles and activity make it look busier and safe from the roads of
abandonment. 

It's just one thought. 
Have I blogged or anything since? No, unfortunately. I'm too busy
writing production code with Perl. But this is the dilemma, ..
How to attract the up-and-coming?  Schools?


-r



-----Original Message-----
From: Steven Lembark [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 19, 2008 11:17 AM
To: [email protected]
Subject: Re: Perl "Going the way of the dinosaur"


Q: In the last two weeks how many of us have changed
   the way we do anything based on this discussion?

Some reasonable ideas were put forward, I'm must
wondering if anyone is actually altering their
actions based on them.

enjoi

-- 
Steven Lembark                                          +1 888 359 3508
Workhorse Computing                                       85-09 90th St
[EMAIL PROTECTED]                                 Woodhaven, NY 11421

Reply via email to