3 ms·

Strange as it sounds, a new language's syntax has become increasingly important and difficult to learn. I learnt a bit of Go during weekends. I love the power

by samblr 9y ago

Strange as it sounds, a new language's syntax has become increasingly important and difficult to learn. I learnt a bit of Go during weekends. I love the power and simplicity of concepts it brings in. But syntax is weird - func args and return is so weird. And variable declaration is verbose. A language's syntax familarity with existing langauges like c, java, pythn, ruby etc.. Helps the speed at which experienced programmers process code. This is not just writing but also reading lot of open source code. If i dont feel upto speed with reading and writing - it kind of discourages.

indescions_2017 9y ago
There's a common refrain you'll hear among Gophers. It goes something like: "I just wrote a 150+ line mind dump. And it successfully built on the first try. No errors. That's never happened before!" So stick with it. It's designed for that level of productivity ;) I feel like I'm learning new concurrency patterns every week or so. Visualization tools like gotrace help, but it's still a mental twizzler. The first time you see chan type os.Signal, or func() or chan chan, you can't help think to yourself "why would anyone do this?" But as you begin to realize its not just about passing data but distributed control flow through your system, you gain more confidence in experimenting.
- Jemaclus 9y ago
  I picked up "Concurrency in Go" (http://amzn.to/2xiGSmi http://amzn.to/2xiGSmi) a few weeks ago. Total game changer on the concurrency part. It totally explains the whole model with a ton of examples and concurrency patterns. I'm still wrapping my head around a lot of it, but my day job code has improved significantly since even my first pass through the book. Highly recommend. I'm still trying to wrap my head around garbage collection and other optimizations that we can make at a lower level. Go is so fun, though.

by samblr 9y ago

indescions_2017 9y ago

There's a common refrain you'll hear among Gophers. It goes something like: "I just wrote a 150+ line mind dump. And it successfully built on the first try. No errors. That's never happened before!" So stick with it. It's designed for that level of productivity ;) I feel like I'm learning new concurrency patterns every week or so. Visualization tools like gotrace help, but it's still a mental twizzler. The first time you see chan type os.Signal, or func() or chan chan, you can't help think to yourself "why would anyone do this?" But as you begin to realize its not just about passing data but distributed control flow through your system, you gain more confidence in experimenting.

Jemaclus 9y ago
I picked up "Concurrency in Go" (http://amzn.to/2xiGSmi http://amzn.to/2xiGSmi) a few weeks ago. Total game changer on the concurrency part. It totally explains the whole model with a ton of examples and concurrency patterns. I'm still wrapping my head around a lot of it, but my day job code has improved significantly since even my first pass through the book. Highly recommend. I'm still trying to wrap my head around garbage collection and other optimizations that we can make at a lower level. Go is so fun, though.