On Tue, Jul 03, 2001 at 04:10:50PM +0800, Selena Sol wrote:
>
> All these things come for free with Java.
>
> In Perl, either they don't come at all or they are not "built-in" to
> the core distribution like they are with Java. And thus...you need
> to roll your own or use CPAN.
>
> Now if, as an organization, you use CPAN, how do you support the
> code? What if there is a security hole in a CPAN module and the
> author is in the middle of final exams? What if you need to extend
> the module with customized features?
What if there is a security hole in part of Java?
If there's a problem which you can fix, you should fix it. Does it
matter what language the problem was written in?
> The fact that these modules are not supported by Perl Inc. means
> that you may feel a bit....hanging over the edge.
Compared to what?
> It is not a secure place to be if you are a CIO.
I suspect that our CIO knows that we use a lot of Perl, and he
probably is quite happy with that.
> If you then look at Java which has a more centralized/controlled
> library, you can at least be sure that the core is supported by Sun
> (although at a high cost).
Cost? Wait a second... Didn't you just say "free with Java" a minute
ago? Which is it? Free or costly?
> But, I think that we as a community should recognize the strengths
> of Java and weakness of Perl.
I don't think anyone would disagree with that. But your economic
argument doesn't make sense to me.
Jeremy
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 439-9951
