this post was submitted on 26 Aug 2023
127 points (97.0% liked)

Technology

63614 readers
3040 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 other!
  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
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
127
Understanding Immortal Objects in Python 3.12: A Deep Dive into Python Internals (codeconfessions.substack.com)
submitted 2 years 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
[–] InvertedParallax@lemm.ee 5 points 2 years ago

It's python, it's supposed to be slow.

Assembly runs the hardware, c kernel runs the assembly, c++ runs the libraries on the kernel, python runs rhe c++, the human runs the python.

Used to write all my uis in c++, but the turnaround time for python is just incredible, write the business logic there, if it turns out you're using it to much lower it to c++.