←back to thread

A tail calling interpreter for Python (already landed in CPython)

(blog.reverberate.org)
122 points phsilva | 2 comments | 17 Feb 25 07:12 UTC | HN request time: 0.42s | source
Show context
VWWHFSfQ ◴[20 Feb 25 04:27 UTC] No.43111138[source]▶
Will Python ever get fast? Or even _reasonably_ fast?

The answer is no, it will not. Instead they'll just keep adding more and more syntax. And more and more ways to do the same old things. And they'll say that if you want "fast" then write a native module that we can import and use.

So then what's the point? Is Python really just a glue language like all the rest?

replies(4): >>43111179 #>>43111277 #>>43111282 #>>43111343 #
1. maxwelljoslyn ◴[20 Feb 25 04:53 UTC] No.43111277[source]▶
VWWHFSfQ, you may already know this, but: I recommend this talk by Armin Ronacher (Flask creator) on how Python's implementation internals contribute to the difficulties of making Python faster.

https://www.youtube.com/watchv=qCGofLIzX6g

One case study Ronacher gets into is the torturous path taken through the Python interpreter (runtime?) when you evaluate `__add__`. Fascinating stuff.

replies(1): >>43112470 #
2. cudder ◴[20 Feb 25 08:39 UTC] No.43112470[source]▶
Your link is broken, here's a working one: https://www.youtube.com/watch?v=qCGofLIzX6g