Messages in this thread | | | Date | Mon, 1 May 2006 13:46:50 -0400 | From | "Dave Neuer" <> | Subject | Re: Compiling C++ modules |
| |
On 4/28/06, linux-os (Dick Johnson) <linux-os@analogic.com> wrote: > > 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.
The cost in developer time is borne every time someone needs to modify the code.
Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |