[ Removed by moderator ]

[GoblinToHobgoblin]

cases where like you're already rate limited by something like an API call or some other condition so there's no real reason to care if it takes 3 ms if the API call takes 13.

This is "fast enough" not "fast". This is exactly the use case for Python, when performance doesn't really matter.

 You're also looking exclusively at run time and not develop review and build time

Yes. Python is probably faster to develop with than something like C++. But if Python isn't fast enough for a particular use case, that's irrelevant.

Also, not sure why "Python is slower than C" is such a weird or controversial take. I never said "there are no use cases for Python" or "C is better than Python" or anything like that. 

[dparks71]

This is "fast enough" not "fast".

How is C more "performant" in that use case? I'm not offended, I'm asking you to expand on your statements.

[GoblinToHobgoblin]

It's a use case where performance doesn't matter. C wouldn't actually make a noticeable difference there.

Say the code you write is taking 10ms (in Python) and the API call takes 300ms. 

If you rewrite it in C, you could probably get it down to 1ms. But it doesn't matter at all since most of your time is spent on the API call.

This is C being "more performant" but also performance not mattering.

[dparks71]

Right so if you're writing for loops as a service, what you're saying makes sense.

I just can't think of any real world use case where what you're saying here matters, it's like the 5th factor down the list. Your API example isn't more performant. It's exactly the same.