in reply to Use Perl wisely, not cleverly
I'm very interested to see your benchmark code, and platform. In purticular, did the perl code have a c-style for loop, or a perl-style? What version of perl was it? Did your C code actualy perform the computation at all, or was it optmized out of existance? Ditto on the Java version. Why do you think this about perl6? Have you seen any benchmarks for parrot? (Try parrot performance vs.(trivial test) the good, the bad, and the ugly to start with. Yes, the perl5 numbers are terrible, but it's outside of it's core competencies by a fair bit. Also, if you change the style a bit to be more idiomatic, it helps quite a bit.) They're quite impressive, and we're still working on them. Did you know that http://amazon.com and http://etoys.com run perl? How about the Human Genome Project? Have you run runtime size comparisons with Java?
If you're doing heavy numeric computing, don't do it in Perl. Do it in C. Integrate the C with perl. But for ordinary, day-to-day computing, perl is a very good choice much of the time.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: [flamebait] Use Perl wisely, not cleverly
by Aristotle (Chancellor) on Feb 20, 2003 at 19:16 UTC | |
|
Re: Re: [flamebait] Use Perl wisely, not cleverly
by petesmiley (Friar) on Feb 21, 2003 at 01:05 UTC |