People want benchmarks. Little graphs that show "Speed", and why it matters to them
C is going to be faster for certain things, Perl for others. Thats a given.
But over half of the speed optimizations one language has over another are useless in any given application.
If you give raw numbers, people apply them to the interpretations they already have.
People need to be told something is better than another -- for THEIR use.
An old argument for writing stuff in python vs java or c, is saying that python executes almost as fast, but is written much quicker -- so you tradeoff a negligible amount of runtime for a large amount of development work.
Thats a compelling argument to get people to use it.
I wouldn't know where to begin, but I'd suggest the following:
Spec out a small little project/exercise - for example
a - a webapp that allows users to register accounts in dbm or mysql, allows them to log in, and post a message on a whiteboard
b - some sort of request processing -- url rewriting or something like that
Time the perl code and c code development
Note the lines of code each required (with and without standard libs)
Run them
a - which one has less resources on the system
b - which one executes faster
c - which one handles more concurrent users
Then show why mod_perl is better based on those results.
On Nov 30, 2004, at 2:47 PM, Clayton Cottingham wrote:
What I am saying , is if you want to open up the mod_perl market you have to
look at why people are not moving to mod_perl
This is a valid reason for not coming over to the mod_perl ranks, because
some people don't see mod_perl as being faster/better than c apps
-- 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
