[gime_tree_fiddy]

Is it just me, or comparing Python's async/await to Go is misleading. As far as I know, even with async/await, Python is still not multicore.

[xapata]

Async IO is solving a different problem than you're complaining about. Python is effectively multicore in nearly every use case. The only trouble is there's no free lunch -- the multicore solution depends on which problem you're facing.

So, what's the issue you're facing?

[stcredzero]

even with async/await, Python is still not multicore.

Even with its channels and scheduler, Go is still not as multicore as Erlang. And I say this as an avid Go user!

[treehau5]

What does something not being as multicore as something else mean?

[gime_tree_fiddy]

Multicore in the sense that the underlying runtime (for the lack of a better word) scales to multiple cores. Like two threads in python cannot run in parallel (like at the same time, not like second one gets scheduled if first one waits for IO or network), the way a goroutine in Golang does.

[stcredzero]

It would be great if the GC was also multicore. As it is, the task of splitting up your application into multiple processes to have more GC still involves too much friction.