Elaine said:
>
> Well, it's would seem that Perl in large corporations is for quick tools
> where we support them ourselves. Noone is going to lose $15 million an
> hour due to a broken SA tool...though they might when Netscape has a
> threading issue on a new version of Solaris and the support teams duke it
> out trying to blame the other before Sun issues a test patch to help
> determine where the issue really is.
>
> Perl just isn't in the same paradigm as Java, et. al. It's useful for what
> it does but it just isn't going to get adopted in the same way as other
> commercial solutions are.
I hear this comment a lot, and I'd like to explore further. Why do you
think it is the case that, in large corporations, Perl is "for quick tools
where we support them ourselves"? Why isn't Perl "in the same paradigm
as Java"? Why do you believe that Perl isn't going to get adopted like
a commercial solution?
Hang on, let's try turning the question around.
Imagine a future world where Perl:
* is adopted in the same way as today's commercial solutions
* is used in large corporations for more than quick self-supported tools
* is considered a fair alternative to Java
How is this future world different from today? Is there something inherent
in the Perl language that has to change? Do we need a Big Company to publicly
proclaim support for Perl?
-Jason
