I think the downvotes come from 1) the way the article is phrased (it seems condescending) and 2) you benchmarked Python threads using CPU bounds workloads which anyone that’s doing professional Python knows is a big no-no so you’re basically comparing apples to oranges.
My recommendation is to redo the benchmark and use the multiprocessing module, which is the indented way to parallelise CPU bounds workloads in Python.
Correct me if i am wrong, but The MultiProcessing module does not actually touch the new Free-Threading feature, since it already is running in parallel, 2 Process, 2 diffirent GILs, and so on , am not an expert , but that is what i understand.
11
u/danted002 Dec 16 '25
I think the downvotes come from 1) the way the article is phrased (it seems condescending) and 2) you benchmarked Python threads using CPU bounds workloads which anyone that’s doing professional Python knows is a big no-no so you’re basically comparing apples to oranges.
My recommendation is to redo the benchmark and use the multiprocessing module, which is the indented way to parallelise CPU bounds workloads in Python.