←back to thread

The first year of free-threaded Python

(labs.quansight.org)
261 points rbanffy | 1 comments | 16 May 25 09:42 UTC | HN request time: 1.101s | 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. rednafi ◴[16 May 25 17:38 UTC] No.44008000[source]▶
I agree about using other languages that have better concurrency support if concurrency is your bottleneck.

But changing the language in a brownfield project is hard. I love Go, and these days I don’t bother with Python if I know the backend needs to scale.

But Python’s ecosystem is huge, and for data work, there’s little alternative to it.

With all that said, JavaScript ain’t got shit on any language. The only good thing about it is Google’s runtime, and that has nothing to do with the language. JS doesn’t have true concurrency and is a mess of a language in general. Python is slow, riddled with concurrency problems, but at least it’s a real language created by a guy who knew what he was doing.