this post was submitted on 26 Feb 2024
31 points (97.0% liked)

Python

6412 readers
3 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

๐Ÿ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

๐Ÿ Python project:
๐Ÿ’“ Python Community:
โœจ Python Ecosystem:
๐ŸŒŒ Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
jnovinger
erlingur
norambna
31
Counting CPU Instructions in Python (blog.mattstuchlik.com)
submitted 9 months ago by [email protected] to c/python
19 comments fedilink hide all child comments
 

Did you know it takes about 17,000 CPU instructions to print("Hello") in Python? And that it takes ~2 billion of them to import a module?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

Same for me. I have used Python for most things since the late 1990s. Love Python. Have always hated the poor performance... but in my case mostly it was good enough. When it was not good enough, I wrote C code.

Python is good for problems where time to code is the limiting factor. It sucks for compute bound problems where time to execute is the limiting factor. Most problems in my world are time to code limited but some are not.

Python compute performance has always sucked.

[โ€“] [email protected] 2 points 9 months ago

I get that... I'm not a developer, I'm a network engineer but I use a lot of python in my day to day operations. I always took python to be the "code for non-coders" which made it infinitely more approachable than some of the other languages.

I'm not running the F1 grand prix over here, I'm driving to get groceries, so what if it's not the fastest thing out there. Close enough is good enough for me. And in my experience that's what people are using python for, daily driving.