Path: ...!feed.opticnetworks.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: David Brown <david.brown@hesbynett.no>
Newsgroups: comp.lang.c
Subject: Re: Baby X is bor nagain
Date: Tue, 25 Jun 2024 19:51:31 +0200
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <v5f033$1ljja$1@dont-email.me>
References: <v494f9$von8$1@dont-email.me> <v53i4s$33k73$2@dont-email.me>
 <v53lf7$34huc$1@dont-email.me> <v53vh6$368vf$1@dont-email.me>
 <v54se1$3bqsk$1@dont-email.me> <20240624160941.0000646a@yahoo.com>
 <v5bu5r$va3a$1@dont-email.me> <20240624181006.00003b94@yahoo.com>
 <v5c86d$11ac7$1@dont-email.me> <JEheO.108086$ED9b.74955@fx11.iad>
 <v5cblg$11q0j$1@dont-email.me> <gEieO.108089$ED9b.25598@fx11.iad>
 <20240625113616.000075e0@yahoo.com> <mUzeO.141609$Cqra.55051@fx10.iad>
 <v5elql$1jmii$1@dont-email.me> <m3BeO.24907$Gurd.16179@fx34.iad>
 <v5empd$1jndv$2@dont-email.me> <v5eph4$1k6a9$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 25 Jun 2024 19:51:32 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="206d13550819d4a97cbe73c199c4d360";
	logging-data="1756778"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX195PpkuvbyuzG1MsmGFXXlkQaKrDSk1X8I="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:yoGTxZpv1q9NLmJxchPXP3trC54=
In-Reply-To: <v5eph4$1k6a9$1@dont-email.me>
Content-Language: en-GB
Bytes: 3685

On 25/06/2024 17:59, bart wrote:
> On 25/06/2024 16:12, David Brown wrote:
>> On 25/06/2024 17:08, Scott Lurndal wrote:

>>>> BTW since you and DB are both keen on products like Python,
>>>
>>> I have never posted anything about python here, that I recall.
>>>
>>> I use it very infrequently.
> 
> (It seemed to be a big part of that 8Mloc project of yours)
> 

I got the impression that it was just for some scripting and automation. 
  I'm sure if Python were not available, he could happily have used 
Perl, or Lua, or Tcl.  I know that's the case for the Python code I 
often have for build automation.

(/I/ have other code for PC and server programs that are in Python, and 
I don't know of any other languages that would suit my needs and wants 
better there.  That's why I chose Python.  But I don't remember Scott 
talking about such code in Python.)

>>
>> I /do/ use Python.  I use it when it is an appropriate language to 
>> use,   which is very different circumstances from when I use C (or 
>> C++). Different tools for different tasks.
>>
> 
> And yet neither of you are interested in answering my question, which 
> was why its simplistic bytecode compiler is acceptable in this scenario, 
> but would be considered useless if applied to C code.
> 

It doesn't often matter that Python code is not efficient - that's not 
why people choose to use Python.  As always, faster is usually better 
when all other factors are equal, but it is rarely an important factor 
for Python code.  There are other ways to make Python programs fast - 
primarily by making sure that the real work is done by underlying C (or 
other compiled language) libraries.

There are oft-claimed rules about how programs spend 90% of their time 
in 10% of the code, or other proportions picked out of thin air.  Python 
is suitable for the 90% of the code where speed doesn't much matter but 
flexibility and ease of development are important, while C is suitable 
for the 10% of the code where speed is important and you're willing to 
pay the cost in development time.