4 ms·
I really enjoyed this, and it also inspired me to try a quick experiment: what would the same blog post look like for Go? I tried it and wrote https://dmitri.s
by dmitshur 7y ago
I really enjoyed this, and it also inspired me to try a quick experiment: what would the same blog post look like for Go?
I tried it and wrote https://dmitri.shuralyov.com/blog/27 https://dmitri.shuralyov.com/blog/27. It was a fun exercise to go through.
- vajrabum 7y agoI did enjoy the article. It was quite clear but it made me wish for a bit more. Unlike the Rust article I didn't see any thing that suggested how golang might be special. I did see your suggestions for further reading though. I'll check them out.
- dmitshur 7y agoThanks for feedback. I think the “special” part for me was that there were large sections of the Rust blog that I could skip having to explain, because they aren’t a part of the Go language. To me, Go is a language that’s much easier to learn and be productive with. Maybe I should make it more clear what I skipped.
- bogomipz 7y agoThanks for sharing. I enjoyed this. Could you elaborate on your closure example though? This was the only one I didn't understand. The explanation is a bit terse = "Closures are just variables with a function type with some captured context." Are these anonymous functions? What is calling the anonymous function if so in main? Cheers.
- dmitshur 7y agoThanks for feedback. I’ll try to clarify that section.