You're right about that. However, I find it easier to understand Go's concurrency model by starting with dataflow and then adding one more requisite (channels),

You're right about that. However, I find it easier to understand Go's concurrency model by starting with dataflow and then adding one more requisite (channels), than starting with classic fork-and-join and then making a bigger jump to message passing concurrency.