On Fri, 28 Apr 2006, Avi Kivity wrote:
>
> If your time is bounded, your Python code might be running while you're
> still typing in your C code, you're be profiling and making changes to
> the alghorithm in Python while hunting for that mysterious segmentation
> fault in C (thank goodness for valgrind), and adding multithreading to
> the third and final version of your Python code while debating whether
> to buy more memory or sit down and chase that memory leak.
>
> Developer performance equates to runtime performance.
>
Read what you wrote! It's absolutely, incredibly stupid!
The cost in developer time is borne once. The cost of performance
is borne every time you run the application.