> In a job interview last year, I was talking to a company who 
> was in the 
> process of moving their big server application to Java from 
> its current 
> Perl base.  They told me they felt like Perl was not ready for 
> professional server environments, but they had had a lot of success 
> with Java.  I'm just passing on what the guy said, but I think it's 
> representative of a common mindset.
> 
> Perl's a subtle and powerful language.  I love that about it, but I 
> think it is pretty easy to do things in less than ideal ways 
> because it 
> gives you so much freedom.  That's a strength and a weakness, 
> I think.  
> A little bit of knowledge can be dangerous.
> 
> Think about it.  How many times do we have to tell people on 
> this list 
> to use strict and warnings, get a module for that, don't slurp big 
> files, etc.  If even a percentage of that is happening in enterprise 
> applications because the coders don't know better, perhaps we can see 
> where some of the thinking comes from.
> 
> Why is it that all the Java guys I talk to know about JSP, but when I 
> mention mod_perl to people they say "Mod what?"  Maybe Perl's public 
> face isn't as strong as some of the alternatives.  Maybe Perl lacks a 
> marketing department, being open source, and that hurts it a little.  
> Don't laugh, I'm serious.
> 

Good point, similar to my "better looking" argument but "better looking" market wise.
That's what we need to do, use shinier words, "Perl Secure Enterprise Edition - 
Leveraging the Power of Experience with Reliabilty ",  that would be the latest Perl 
that always has 'use strict' and 'use warnings' running no matter what 
the script has in it:
IE #/usr/bin/perl 
print "hi"; 

Maybe a warning gets spit out if the file they are slurping is 
over a certain size, also.
And You'd need to use shiny words for describeing it's features:
"Exponentially expand the ease and practicality of development, deployment,
and use with many powerful modules that help you get the job done faster, and more 
securely."
"Complies with industry standards and functionality."

You'd have to have a cli (running on our Perl S.E.E of course) for each platform that:
        - lists/upgrades/installs modules
        - upgrades to latest "Perl S.E.E." with one click/command

Have the binary be called perlSEE instead of perl or something.

Looks like we have a busy weekend ahead!

> Of course, that's all just guess work on my part.  I'm no expert.
> 
> On the flip side, I believe Amazon.com uses a mostly Perl 
> system, just 
> to name a familiar name.  There has to be others, I would think.
> 

Maybe a website listing should be made/found??

> James
> 
> 
> -- 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED] 
<http://learn.perl.org/> <http://learn.perl.org/first-response>



--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>


Reply via email to