Gophers, what parts of Go did you find/are you finding challenging to learn?

Comments

[Vicent]

The true power of interfaces

[Eduardo Hitek]

That's my case! I (probably) know how to write and to use, but now sure how to maximize the benefits of it. =/

[William Antonelli]

The basic concept of interfaces. I don't see a reason I would ever use them, yet I'm sure I should be using them. I've read multiple articles (dozens) and still don't understand how/when I should implement them.

[Yechiel Kalmenson]

Pointers took me some time to wrap my head around.

Also, coming from Ruby where interfaces are more of an implicit concept, having to define them explicitly in Go was frustrating at first.

[Andy Haskell]

Interesting, implicit concept like how you pass in a Ruby value and it runs methods that are expected to be there?

[Yechiel Kalmenson]

Yeah, the idea of duck typing, where as long as an object responds to certain methods and had certain values it can be replaced with any other object, no matter the type, that implements the same methods and properties, without that interface having to be explicitly defined anywhere.

When I was doing Ruby I used to love the flexibility that me, now I can't imagine how anyone can maintain that lol.

[Steve Layton]

Interfaces and channels. I still have to stop and think every time I go to use them.