Here's a little data just to ground things a bit: $ time dash -c ''
real 0m0.001s user 0m0.000s sys 0m0.000s $ time rc -c '' real 0m0.002s user 0m0.000s sys 0m0.000s $ time bash -c '' real 0m0.007s user 0m0.003s sys 0m0.000s $ time python -c '' real 0m0.028s user 0m0.017s sys 0m0.007s When we're talking about a small script with trivial running time (which is not necessarily the case here), the 10x slower startup time for python does make a difference when you're programmatically executing the script several thousand times. One can argue in that case that the calling script itself should be written in python to avoid the repeated start-up, but that breaks modularity. I love python but on my older machine I definitely feel its "bloat." On Thu, Jan 20, 2011 at 10:30 AM, Kurt H Maier <karmaf...@gmail.com> wrote: > On Thu, Jan 20, 2011 at 9:13 AM, John Yates <j...@yates-sheets.org> wrote: >> What is the largest corpus of code you have authored? What is the >> largest corpus you did not author yet had to master? At large scale >> the choice of language makes a big difference. > > thank you, john, for your completely irrelevant questions, and their > contributions to this discussion of non-large-scale programming. > > -- > # Kurt H Maier > >
