[belluchan]

Cool, but I'd say Go is easy to learn. You can power through the spec, read Effective Go, figure out the go tools and GOPATH and be on your way. There's so little cruft. Go is limited in some ways, but the benefit is how simple it is.

With a language like JavaScript it can take a really long time to learn all the stupid stuff like when what this means. With Python it can also take a long time before you start having to figure out the various string representations, operator overloading and the crazy underscore variables. That kind of magical hidden complexity you see in other languages I don't think exists in Go, which makes it easy to learn.

With Go, I feel at least you can learn all that is Go in a week or so, and start building. Something like the "learn ruby/rails in 30 days" would never make sense to me given how easy it is to learn Go.

A lot of the expertise you see in Go comes from people who really know about the Go implementation. The way structs are represented in memory on different hardware, compilation optimization, the crazy stuff that most people are just not going to care about especially if they're going to run Go on some kind of cloud provider or in a vm.

[simias]

I don't know much about Go but even a very small language like scheme can fuel quite a lot of screencasts if you put your mind to it. And Go is huge compared to a lot of scheme implementations.

It's not so much about learning all the syntax of the language on its own (which is useless and boring) but rather about how using the language to solve some real problems.

[ScottWhigham]

What I've learned about learning is that it's a very personal thing. People learn their way, not the way you think is the "best" way (and I mean the collective you, not you personally). Which is the best way to get started learning something? The way that you are comfortable with and the way that you see yourself continuing the learning process.