> CPython has had a GIL for the past 30 years - and things worked out just fine. No, they did not. That's why the discussion about the GIL is about as old as

> CPython has had a GIL for the past 30 years - and things worked out just fine. No, they did not. That's why the discussion about the GIL is about as old as Python3 itself. The GIL has always been a major drawback of python, moreso because the language does in fact have threading support...only it can't use threads for parallel workloads. This drawback was tolerated, because of the many advantages Python brings to the table, and because Python comes from an age when Moores Law was still in full effect; Powerful single cores were the norm not so long ago. This isn't the case any more. Moores Law is done. Now we increase the number of cores, and languages that wish to remain relevant, need to reflect that.