I think this is a reasonable point, and of course you could take it further and say that assembly language is better than functional programming when you're doi

I think this is a reasonable point, and of course you could take it further and say that assembly language is better than functional programming when you're doing work that requires you to reason about what the CPU is doing exactly. But I would argue that the majority of Go programs should not require the programmer to follow the intimate details of a program's execution when trying to understand the business logic. The fact that the language has a garbage collector would suggest that it was designed for programs where some details can be hidden away. So I agree with your general point, but I am somewhat skeptical about its application to Go.