▲ -2 ▼ Relying on Go (antonz.org) submitted 3 months ago by CodiUnicorn@programming.dev to c/golang@programming.dev 6 comments fedilink hide all child comments
[–] cockmushroom@reddthat.com 1 point 3 months ago (1 child) Concurrency isn't parallelism permalink fedilink source parent hideshow 1 child comment replies: [–] atkdef@lemmy.dbzer0.com 1 point 3 months ago True, and that's exactly why I said parallelism. Concurrency without parallelism is just like Python/JS, a single thread drives all the coroutines, and it's the easier one, as the runtime doesn't really need to lock. GO on the other hand has parallelism. It maps goroutines to a thread pool, which requires locking, making things more complicated. This is also why Rust has two types of reference counting, Rc and Arc. permalink fedilink source parent
[–] atkdef@lemmy.dbzer0.com 1 point 3 months ago True, and that's exactly why I said parallelism. Concurrency without parallelism is just like Python/JS, a single thread drives all the coroutines, and it's the easier one, as the runtime doesn't really need to lock. GO on the other hand has parallelism. It maps goroutines to a thread pool, which requires locking, making things more complicated. This is also why Rust has two types of reference counting, Rc and Arc. permalink fedilink source parent