I took it to mean he launched several copies of the process, each copy pinned to one (and only one) core.
Correct it was the only way to get Go to scale to a reasonable response rate for this application and it thus meant my CPU loading was not even since it was based on the randomness of socket connections that persisted on one cpu or another.
He's not talking about merely being able to use channels in one core setup. This misunderstanding made me question your whole comment.