Concurrency is not Parallelism by Rob Pike

Channel:gnbitcom · Length:31:22 · Published:2015-11-11 · Views:191401

Watch on YouTube

Summary

Rob Pike's Go talk distinguishing concurrency, the structuring of independent processes, from parallelism, their simultaneous execution. It uses Go channels and goroutines to illustrate.

Why HN recommends it

The standard link for explaining the concurrency versus parallelism distinction and the motivations behind Go's concurrency model.

here's an excellent talk on the same subject by Rob Pike that I link all the time to people — HN, 2024

C, C++, Rust, Go & systems languages · Software architecture & design

Subtitles (excerpt)

you if you looked at the programming languages of today you probably get this idea that the world is objectoriented um but it's not it's actually parallel um you've got everything from the lowest level like multicore machines and up through networking and so on so but it gets all the way up to users who knows planets the universe there's all these things that are happening simultaneously in the world and yet the Computing tools that we have are really not very good at expressing that kind of worldview and that seems like a failing but we can fix that if we understand what concurrency is and how to use it now I'll assume that most of you at least heard of the go programming language is just what I've been working on at Google the last few years and go is a concurrent language uh which means that it has some things in it to make concurrency useful like it's got the ability to execute things concurrently the ability to communicate between things that are executing concurrently and it's got this thing called a SEL statement which is a multi-way concurrent control switch if that doesn't make any sense to you yet don't worry but when we announced go which was about 2 years ago all these uh programmers out there

On Hacker News

If you prefer to learn by video, here's an excellent talk on the same subject by Rob Pike that I link all the time to people [VIDEO] — duped, 2024-09
Agreed. Rob Pike presented a good talk "Concurrency is not Parallelism" which explains the motivations behind Go's concurrency model: [VIDEO] Between the lack of "colored functions" and the simplicity of communicating with channels, I keep surprising myself with how (relatively) quick and easy it is to develop concurrent systems with correct behavior in Go. — auxiliarymoose, 2025-12
Anyone that can wrap their mind around the model of Communicating Sequential Processes[1] implemented using channels in Go will improve their programming. See also Concurrency is not Parallelism by Rob Pike: [VIDEO] After I figured it out, I spent a good month writing personal projects to play with channels and concurrency and get the "these are cool I'm going to use them everywhere" urge out of … — cratermoon, 2022-10
yeah, basically. a lot of people do not know, but async/await does have NOTHING do to with threads or processes. you can use threads with async/await, but you do not. async/await basically means you are running your "green threads"/tasks/promises on a event loop, the event loop can be either single threaded or it can run the stuff on multiple threads. a lot of people just did not get the differen… — merb, 2021-06
Sure, but the context is very important: you can use Rust to control the DOM from WASM [1] and then you can use Haskell to write a load balancer [2]. [1] [LINK] [2] [LINK] (off-topic: Rob Pike's Concurrency is not Parallelism [VIDEO] ) — ly3xqhl8g9, 2023-03

Related videos