> Honestly? Not everyone wants (or should have) to do that in order to touch some Go code
For hobby projects maybe, if it's part of your job you should know what you're doing and read the fine manual (basic documentation in this case).
For hobby projects maybe, if it's part of your job you should know what you're doing and read the fine manual (basic documentation in this case).
I cannot stress enough that not all programming occurs in a work or even social context.
Besides, I did not say Go is hard to pick up. I said people should not need to read the entire manual, so to speak, to do things involving Go or any other language or tool. Cheat sheets like the linked article that outline the language in terms of "things you need to know as someone who already programs extensively" are thus actually quite helpful. That is all.