On Aug 10, 2004, at 21:28, Eric Lenio wrote:
the reason I'm asking is because the client is really more attuned to the java
hype/buzzwords that exists out there. having done just a smattering of java, I
am somewhat at a loss as to tell them exactly why a perl solution is better.
this client does already have some investment in java, but no perl, so it is
probably more palatable to management to continue to invest in java.
Looks like the typical set of advantages we Perl coders find valuable might not be of interest to your client. Because he does not have to write the application, and has staff and preferences for Java.
He probably doesn't care much about CPAN for this particular project, for instance, perhaps he just wants an application that fulfills the requeriments and they can maintain. You are the best person to judge that.
Since one of the key advantages of Perl is speed in development, if the project is paid by hours perhaps you could offer a cheaper price for the Perl implementation than for the Java implementation. That could interest to him maybe.
Writing what you described in CGI.pm under Apache::Registry with TT2 looks way more quick and bug-free than writing it in Java/JSP provided you are equally fluent in both.
But if you still would like to convince your client, perhaps you could borrow some ideas from this paper:
Dynamic Languages: Ready for the Next Challenges, By Design
http://www.activestate.com/Company/NewsRoom/whitepapers_ADL.plexthe client is also quite concerned with scalability, but I am confident that mod_perl will scale extremely well.
I am confident too, Slashdot runs on Perl for instance, but have no personal experience in heavily loaded websites.
-- fxn
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
