I found it helpful. It did confirm my priors (Go is useful for a big class of problems) and educate me a bit (uninitialised values set to zero??)
I have compiled some Go (so fast) but written zero Go. I do not like garbage collected languages, but rather a garbage collector than reference counting (I have done a lot of Swift - Why? For money - there could be no other reason)
> I'd love it if you could summarize the thoughtful constructive criticism you saw for the rest of us.
The lack of protections for using uninitialised data structures. I learnt about that from this article. Makes me nostalgic for C
I found it helpful. It did confirm my priors (Go is useful for a big class of problems) and educate me a bit (uninitialised values set to zero??)
I have compiled some Go (so fast) but written zero Go. I do not like garbage collected languages, but rather a garbage collector than reference counting (I have done a lot of Swift - Why? For money - there could be no other reason)
> I'd love it if you could summarize the thoughtful constructive criticism you saw for the rest of us.
The lack of protections for using uninitialised data structures. I learnt about that from this article. Makes me nostalgic for C