←back to thread

The first year of free-threaded Python

(labs.quansight.org)
253 points rbanffy | 2 comments | 16 May 25 09:42 UTC | HN request time: 0.592s | source
Show context
henry700 ◴[16 May 25 17:12 UTC] No.44007770[source]▶
I find it peculiar how, in a language so riddled with simple concurrency architectural issues, the approach is to painstankingly fix every library after fixing the runtime, instead of just using some better language. Why does the community insist on such a bad language when literally even fucking Javascript has a saner execution model?
replies(4): >>44007818 #>>44007823 #>>44007847 #>>44008000 #
1. forrestthewoods ◴[16 May 25 17:18 UTC] No.44007823[source]▶
> instead of just using some better language

Python the language is pretty bad. Python the ecosystem of libraries and tools has no equal, unfortunately.

Switching a language is easy. Switching a billion lines of library less so.

And the tragic part is that many of the top “python libraries” are just Python interfaces to a C library! But if you want to switch to a “better language” that fact isn’t helpful.

replies(1): >>44009750 #
2. kubb ◴[16 May 25 20:54 UTC] No.44009750[source]▶
I wonder if we get automatic LLM translation of codebases from language to language soon - this could close the library gap and diminish the language lock in factor.