I am sure Go can do at the very least 2x-3x vs node for the same workload.
CPU bound? For sure.
Fake CPU bound (as this one is, spending tons of time in go's concurrency machinery), clearly not.
I/O bound? I would have said no before Spectre and Meltdown ruined all our intuitions about performance. It's just a mess right now.
1: There's basically one way to do anything, even if you pull in a library that collects those one ways to do another thing.
2: Those one ways are each developed by some of the most skilled engineers in the world and documented by someone with amazing clarity. (https://golang.org/pkg/)
I have always had a lot of trouble trying to learn to program (used to struggle more with focus and memory), but Golang is just easy. I can look at an API I wrote as a learning project after 6 months of not writing any code and understand it perfectly.
Node was not so bad when things worked, but I hit the same brick wall I did with [insert language] when something didn't go like the guide said it should.