<story><title>Go turns three</title><url>http://blog.golang.org/2012/11/go-turns-three.html</url><text></text></story><parent_chain></parent_chain><comment><author>lbarrow</author><text>We&apos;ve been playing around with Go where I work. The concurrency model is great, and the type/object/interface approach is pretty flexible. The language designers also succeeded in eliminating many of the pain points they felt with C/C++/Java: dependency bloat and compilation speed. My workflow with Go has more in common with an interpreted language than anything else.&lt;p&gt;However, the lack of generics seems like a pretty bad oversight. It&apos;s annoying to rewrite common functional operations (e.g. map, reduce) over and over again  with slightly different argument types (or sprinkling type casts all over your code).</text></comment>
<story><title>Go turns three</title><url>http://blog.golang.org/2012/11/go-turns-three.html</url><text></text></story><parent_chain></parent_chain><comment><author>jgrahamc</author><text>Congratulations to everyone involved with Go. I&apos;ve been loving using it and it&apos;s nice to see CloudFlare mentioned in that post as we are using Go more and more for our production systems.</text></comment>