Someday we will set aside our optimization focus. Our architectural validation probe will be complete. We will have established that yes, the parrot design can support the required speed. Further optimization will be seen as premature optimization.
Optimization, in and of itself, is rarely a bad thing. That whole 'premature optimization' quote gets slung around and like so many other aphorisms it's almost correct. (The quote ought to be "inappropriate optimization is the root of all evil" but inappropriate's a much fuzzier word than premature, though premature itself is hard to gague)
As far as I'm concerned, people are welcome to dig in and optimize the heck out of code, with the caveat that they don't make a mess. That is, APIs should be respected, and the code in question should be replaceable. Optimizing data structures is a trickier thing, and for that I'd prefer more discussion before things are done, as exposed structures are more difficult to change later. Code, structures, and API in that order for what's acceptable.
Besides, like it or not, programmers like to fiddle. Better to have an approved place than not...
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
