> Though personally, I think Success Stories are overrated. If I know
> Perl is good, then I will use it. I don't have anything against them, I
> just don't find them very interesting from the perspective of "can Perl
> do this?", because I know that Perl can do that.
What I sense here is (could be wrong) that we need to distinguish between
advocating Perl to ourselves versus advocating Perl to MIS shops that aren't
currently using it, and are hopefully investigating migration paths from
existing development technologies. Those things might not be interesting to
you, Chris, because you are very accomplished in this area. I would be
advocating to someone not already aware of Perl's potential.
> Check the www.perl.com site.
I have, for many years now. I still feel the site caters to growing Perl
developers, .... which is crucial and effective. That's part one. However, I
still feel there is a place for people investigating Perl to read some Case
studies, "why is Perl effective?", and evangelistic like things. There are
some around the main Perl sites, ... but it doesn't seem to stand out or be
as promoted as I would hope. The success stories that are there are nice, I
have read and I do value them. But, ...
>
> I think it is most correctly noted that being a *programmer* is safest
> for one's career as a developer. No one should stick to one language if
> this is their career path.
You are indeed correct. However, what my staff is facing is 100% Perl based
programming (granted, Javascript, HTML, XML in the mix). Unlike some other
environments, there aren't many 100% Perl based programming jobs out here in
Colorado. Instead, Unix sysadmins with Perl experience might have easier
placement. Or DBA's as the primary with Perl and C skills to augment.
However, 100% Java development environments are hiring for full-time
positions without syadmin or other work. As you mentioned, this may not be
true in a few years but it is certainly a current issue. And maybe this is
because with Perl, you get your Job done faster and need to earn the rest of
your keep with other duties! ;-)
>
> > Perception is reality.
>
> No, it isn't. The reality is that Perl is the #1 language used on the
> web. The perception is that it is not used very much, or isn't very
> imporant.
Perception is reality to the persion perceiving. If you think you see a tiger
in front of you, your emotions react accordingly, regardless if it is a
hallucination or a trick. If people believe that Java is enterprise ready and
Perl is fading, then they would act accordingly regardless of the truth. I'm
not saying that people have that perception, but thay may have any number of
incorrect perceptions.
It should be up to this advocacy group to combat misperceptions or prevent
misinformation by increasing knowledge of truth. This, of course, done by
advocating Perl's usage and evangelizing Perl to fellow developers who might
really improve their lives by giving Perl a chance. Once their mind is open
to the possibility that Perl might be a viable solution, then they would
usually investigate it. How do they do that? Find out who is *effectively*
using Perl for real world problems and solutions. Find out the claimed Merits
of Perl. Grab a book and try some code. They're limited to what they are
exposed to at first. Getting their ears and eyes willing to listen and learn
might start with exposure by ads, articles, testimonials, etc. in the areas
that they frequent. (trade rags?)
>I don't care about perception. I care about getting my job
> done, and as long as I can demonstrate to my (?:potential)? employer
> that I will get my job done, then I am set.
One's reality and truth can be different entities. I understand and agree
with your last statements here (from one's own perspective), but we aren't
trying to evangelize Perl amongst ourselves as much as to the world abroad;
non-Perl aware people.
Just some thoughts
Rod
