this post was submitted on 26 Aug 2023
111 points (95.9% liked)

Technology

59419 readers
5352 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
L4s@lemmy.world
L3s@fry.gs
L4s@fry.gs
enu@lemmy.world
111
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
7 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 4 points 1 year 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++.