On Tue, Sep 12, 2000 at 12:46:55AM -0500, J. David Blackstone wrote:
> http://dev.perl.org/pm/pos.html mentions the following risk in perl6
> development:
>
> > 4.We produce a slower interpreter.
>
> It is very easy to create something that is unacceptably slow and
> not realize until toward the end of the process.
True, true. A good idea to set up the benchmarks and run them periodically.
My only concern is that they might touch of premature optimizations.
That when a new feature is initially added it might slip on a
benchmark and the implementors will be driven to cut corners to make
it faster causing a deficiency in the design and maintenance.
It'll mostly be a matter of psychology. We can't present the
benchmarks early in the process as "OH MY GOD THIS IS SOOOO SLOW!" nor
should we emphasize its differences with Perl 5 (not until feature
freeze).
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
Maybe they hooked you up with one of those ass-making magazines.
-- brian d foy as misheard by Michael G Schwern
