William R. Ward [[EMAIL PROTECTED]] quoth:
*>
*>My primary client is refusing to use Perl in its next generation
*>product - only because Java has more "buzzword value." And this is
*>not the first time I've heard this issue.
Dont forget, too, that a large part of the Java attraction for web
hosting/e-commerce is the large number of packaged products that either
use Java or ship with a Java API. There are a lot of reasons Java looks
more attractive to corporate entities than Perl.
Does Perl really have value in the product that your client has? Perhaps
Java is a more popular and more often used feature than Perl. Is it
something customers could voice an opinion about?
*>Web scripting was the killer app that got Perl to where it is. We
*>can't afford to lose it.
I have done a bit of research on this and have found little to support
this idea past 1994 which was well before the ubiquity of the net. Java
came along and Sun sent people to training for free, got vendors to add
the Java API to their products, etc. In the big world of e-commerce and
web hosting, very few use Perl except for glue here and there and system
administration. When there is little professional support, clpm, matt
wright rants, no product integration, no out-of-the-box web design or
e-commerce tools, and a myriad of other potential issues, is it really any
wonder that Java is more often chosen? Would hype really fix that?
If you want Perl6 to be the next Java then take a close look at how Sun
designed its success in the marketplace.
e.
