3 ms·
It's very easy to pick up. The parts you might find weird are mainly: 1) The OO model (composition-over-inheritance, and the syntax may be a little unfamiliar)
by yamtaddle 4y ago
It's very easy to pick up. The parts you might find weird are mainly:
1) The OO model (composition-over-inheritance, and the syntax may be a little unfamiliar)
2) Slices
3) Goroutines/concurrency
4) I guess multi-return and idiomatic error handling deserve a mention, though they're so minor and super easy to understand that they're not really like the other entries on this list.
... but if you can devote 2-3 hours to reading the official manual for each of those topics and working through an exercise or two for each, congrats, you're ready to work productively in Go. Maybe 20 hours total, at the outside, to get comfortable enough to use it productively. Possibly closer to 10. Assuming some prior familiarity with other similar-family languages, that is, which most developers have.