this post was submitted on 26 Aug 2023
128 points (97.1% liked)

Technology

59108 readers
3267 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
128
Understanding Immortal Objects in Python 3.12: A Deep Dive into Python Internals (codeconfessions.substack.com)
submitted 1 year ago by abhi9u@lemmy.world to c/technology@lemmy.world
14 comments fedilink hide all child comments
 

A detailed examination of Python 3.12's internal changes featuring the concept of 'immortal' objects, for performance enhancements

you are viewing a single comment's thread
view the rest of the comments
[–] fartsparkles@sh.itjust.works 59 points 1 year ago* (last edited 1 year ago) (1 children)

Python isn’t used for the problem space of speed… Try using PHP for data science visualisation. Need a library to solve a problem? Ruby probably doesn’t have it. Need to write a quick script to transform some data? Better spend more time than doing it manually as you accidentally allocate memory incorrectly in C++. Want to scrape a website for some text? Enjoy tonnes of boilerplate and 30 lines of Java vs the three lines of Python.

Python isn’t about speed, it’s not even about being the best at anything, it’s about being good enough at pretty much any task your average coder needs to pull off in as short a time as possible, all with a single language. Plus, it’s way easier to bounce to another language from Python should you need to (for instance it’s much easier to write a speed-critical component in Go vs the entire application stack in Go - Python has a much lower cognitive load and developers can easily extend or refactor thanks to Pythonic code).

The amount of Python libraries that are actually written in C is huge and Python makes no attempts to suggest it’s more performant than something like C - why do you think Python bindings even exist?

Thinking speed is a ding on Python shows a gross lack of knowledge of Python and its purpose.