On: Let's Remove the Global Interpreter Lock

[nine_k]

You have web workers, generators, all the async stuff, futures and promises — plenty enough from the language perspective. Maybe node.js does not happen to be multi-threaded, but it's not about the language.

[jerf → nine_k]

That's all true about Python, too, and it's been true since before Node existed. If Node were adequate, Python would be adequate too.

In fact, other than "run lots of Javascript", I'm not sure I can name a single thing Node did before Python.

[heavenlyblue → nine_k]

By the same logic Python is multithreading-ready as well, since it's only a matter of it's major implementation why it doesn't support multithreading.

[nine_k → heavenlyblue]

> By the same logic Python is multithreading-ready as well, since it's only a matter of it's major implementation why it doesn't support multithreading.

How web workers aren't threads? Browsers are more widely deployed than Node, even with the same V8 engine.