From: Michael Campbell <michael.campbell@...>
Date: 2005-06-13T01:25:35+09:00
Subject: Re: python/ruby benchmark(don't shoot the messenger)

On 6/12/05, Alexandru Popescu <the_mindstorm@evolva.ro> wrote:


> Also, I agree with the fact the optimization comes later in the dev cycles. But we need to have the
> doors open to optimize. Moreover, I read that in Ruby you can always go and code the hot spots in C.
>  What if you don't have these resources? Which are the costs to bring such a resource and make him
> productive?

How does this issue relate to *ruby*?  The same charge could be levied
at python, even J2EE.  "What happens if you don't have the resources
to speed up something slow?"

I tend to agree with Austin on this; theoretical, academic arguments
don't mean much when a customer wants his software.

It surprised me coming up through the application development
(financial applications) world, but some customers even *WANT* early
releases to be slow, so they can feel good that they tell the
developers to make it faster, and they do.