> Our team tried to advocate Perl for an internal enterprise
> web application, and failed, I would say that amazon.com may
> have clinched it (just didn't find out in time) We developed
> a prototype site in Perl/mod_perl/linux etc -
> >40000 lines of new code, 2 engineers, 6 weeks - almost fully
> functional
> (>90% of feature set). The rest of the "proper engineers" are
> still arguing about the implementation of the "proper site"
> in a "proper language" - java, one year, 7 engineers and no
> code (well one failed repository of code).
Yes, that's a common enough story. I have encountered this several
times: pitch to prospective client a web-project built on Linux, Apache,
MySQL, mod_perl. Client reviews pitch... Okays Linux and Apache. Talks
for a long time about Oracle instead of MySQL. Checks pricing on Oracle
and then okays MySQL... and then... Decides not go with the "scripting"
language, but opts for a Java or .Net solution.
In the meantime a couple of programmers here have built a virtually
fully-functioning prototype to demonstrate to potential client and for
benchmarking. Client still decides he wants a "proper" programming
language. Months (and thousands of man-hours) later and the client has
nothing to show for the effort.
It never ceases to amaze me how many prospective clients come back to us
after they've tried (and failed) with an alternative implementation.
This happens frequently enough for us to be able to justify the
man-hours committed to prototype development.
Long live mod_perl.
Jonathan M. Hollin
Digital-Word Ltd
(
http://digital-word.com/)
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org