Rob Pike tried to create a distinction here: https://go.dev/talks/2012/waza.slide#1 https://go.dev/talks/2012/waza.slide#1 Using his distinction, concurrency i

Rob Pike tried to create a distinction here: https://go.dev/talks/2012/waza.slide#1 https://go.dev/talks/2012/waza.slide#1 Using his distinction, concurrency isn't about IO-boundedness (though that's a common use-case for it), but instead is about composing multiple processes (generic sense). They may or may not be running in parallel (truly running at the same time). On a unix shell this would be an example of concurrency, which may or may not be parallel: $ cat a-file | sort | uniq | wc Each process may run at the literal same time (parallelism), but they don't have to, and on a single core machine would not be executing simultaneously. This hasn't fully caught on, though.