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. Our focus will
shift to making parrot actually
Mitchell N Charity [EMAIL PROTECTED] wrote:
... Our focus will
shift to making parrot actually work. To giving it
working exceptions, io, embeddablility, and so on.
Given Leo's numbers, it seemed a possibility worth suggesting.
I can certainly imagine other policies. Like focusing on
Mitchell N Charity wrote:
Further optimization
will be seen as premature optimization. Our focus will
shift to making parrot actually work.
If we never optimize, we won't have the speed to run real-world
programs. But if all we do is optimize, we won't have the features to
run real-world
Brent 'Dax' Royal-Gordon [EMAIL PROTECTED] writes:
Other times, we add lots of new features, and then stop to test them
and find they're incredibly slow. (That's objects right now.)
In objects' defence, I'd just like to say that they are rather lovely.
