On Tue, 2008-02-12 at 21:36 -0500, Bob Rogers wrote:
> From: chromatic <[EMAIL PROTECTED]>
> Date: Tue, 12 Feb 2008 17:03:31 -0800
>
> On Tuesday 12 February 2008 16:55:06 Geoffrey Broadwell wrote:
>
> > Feh. Please someone tell me there is a light at the end of this tunnel?
>
> Don't worry. Parrot will give Rakudo a whole different set of performance
> problems than Perl 5 has.
Heh. At least my life will still be Interesting ... too bad about the
capital letter there. Maybe if I learn all of the Rakudo performance
problems by the time the production release comes out, I can charge an
arm and a leg in consulting fees to people trying to figure out how to
get their Perl 6 code to perform well. :-)
> No doubt. And when there are concrete performance problems on the
> table, in a Parrot nearing production release, then removing barriers to
> inlining will provide a solid reason to reopen some design decisions.
Hmmph. (That's a good natured grumble, but still a grumble.)
Here's my fear: Parrot will near production release, we'll start
finding performance problems, and everyone will be so incredibly ready
to get 1.0 out the door that we'll release before fixing them ("correct
now, fast later" and all that). Unfortunately, we'll find out after the
release that the only way to fix the performance problems is to make
some deeply incompatible change, and suddenly we'll be staring down the
barrel of the production release compatibility shotgun.
I dunno how likely that is -- fears are irrational beasts after all --
but there it is.
On a more rational note, has any thought been given to what "good enough
performance for release" will be? Or to put it pessimistically, how bad
does a performance problem have to be before it will be considered a
release blocker?
-'f
