title: Concurrency is not Parallelism?
body: <p><a href="http://concur.rspace.googlecode.com/hg/talk/concur.html#title-slide" rel="noreferrer">Here</a> are slides by Rob Pike on this. Every time I go thru this I feel like a moron. I'm not able to to figure out the gist of it. It's well understood that concurrency is decomposition of a complex problem into smaller components. If you cannot correctly divide something into smaller parts, it's hard to solve it using concurrency. </p>
  
  <p>But there isn't much detail in slides on how to get parallelism once you've achieved concurrency. In the Lesson slide (num 52), he says Concurrency - "Maybe Even Parallel". But the question is - <strong>When and How can concurrency correctly and efficiently lead to Parallelism?</strong></p>
  
  <p>My guess is that, under the hood Rob's pointing out that developers should work at the level of concurrency - and parallelism should be language's/vm's concern (gomaxprocs?). Just care about intelligent decomposition into smaller units, concerned only about correct concurrency - parallelism will be take care by the "system".</p>
  
  <p>Please shed some light.</p>