<story><title>Go is my hammer, and everything is a nail</title><url>https://www.maragu.dev/blog/go-is-my-hammer-and-everything-is-a-nail</url></story><parent_chain><item><author>conor-</author><text>Go is the only language I&amp;#x27;ve ever felt highly productive working in. Oftentimes in other stacks I find myself in analysis paralysis on meta things that don&amp;#x27;t matter:&lt;p&gt;- what design patterns&amp;#x2F;language features make sense to use&lt;p&gt;- what is the best lib to accomplish X&lt;p&gt;- how do you keep things up to date&lt;p&gt;With Go, the language is so simple that it&amp;#x27;s pretty difficult to over engineer or write terse code. Everything you need is in stdlib. The tooling makes dependency management and upgrades trivial because of strong backwards compatibility.</text></item><item><author>daghamm</author><text>The author lists multiple reasons for this, but for me the biggest one is the first one: Go is good for almost &lt;i&gt;everything&lt;/i&gt;.&lt;p&gt;I have extremely good productivity when using Go. Once your project exceeds 100 lines it is usually even better than python. And yes, I am aware that Rustians did a survey where Rust was crowned as the most efficient language but in my reality (which may differ from yours) Go is simply the best tool for most tasks.&lt;p&gt;Why is that? Well, for me there are 3 reasosns:&lt;p&gt;1. The language is extremely simple. If you know 20% of C you are already a Go expert.&lt;p&gt;2. The core libraries are extremly well thought.&lt;p&gt;3. Batteries are included. The toolchain and the core libraries alone can do 90% of what most people will ever need.&lt;p&gt;When people argue about the validity of these claims, I simply point them to this talk &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;go.dev&amp;#x2F;talks&amp;#x2F;2012&amp;#x2F;concurrency.slide#42&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;go.dev&amp;#x2F;talks&amp;#x2F;2012&amp;#x2F;concurrency.slide#42&lt;/a&gt;</text></item></parent_chain><comment><author>pjmlp</author><text>Sure, if everything one does is either CLI stuff, or UNIX daemons, containers, ....&lt;p&gt;Because in the reign of graphics , GUI, GPGPU, HPC, HFT, ML, game engines,numeric analysis, ... there is hardly any library that really stands out.</text></comment>
<story><title>Go is my hammer, and everything is a nail</title><url>https://www.maragu.dev/blog/go-is-my-hammer-and-everything-is-a-nail</url></story><parent_chain><item><author>conor-</author><text>Go is the only language I&amp;#x27;ve ever felt highly productive working in. Oftentimes in other stacks I find myself in analysis paralysis on meta things that don&amp;#x27;t matter:&lt;p&gt;- what design patterns&amp;#x2F;language features make sense to use&lt;p&gt;- what is the best lib to accomplish X&lt;p&gt;- how do you keep things up to date&lt;p&gt;With Go, the language is so simple that it&amp;#x27;s pretty difficult to over engineer or write terse code. Everything you need is in stdlib. The tooling makes dependency management and upgrades trivial because of strong backwards compatibility.</text></item><item><author>daghamm</author><text>The author lists multiple reasons for this, but for me the biggest one is the first one: Go is good for almost &lt;i&gt;everything&lt;/i&gt;.&lt;p&gt;I have extremely good productivity when using Go. Once your project exceeds 100 lines it is usually even better than python. And yes, I am aware that Rustians did a survey where Rust was crowned as the most efficient language but in my reality (which may differ from yours) Go is simply the best tool for most tasks.&lt;p&gt;Why is that? Well, for me there are 3 reasosns:&lt;p&gt;1. The language is extremely simple. If you know 20% of C you are already a Go expert.&lt;p&gt;2. The core libraries are extremly well thought.&lt;p&gt;3. Batteries are included. The toolchain and the core libraries alone can do 90% of what most people will ever need.&lt;p&gt;When people argue about the validity of these claims, I simply point them to this talk &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;go.dev&amp;#x2F;talks&amp;#x2F;2012&amp;#x2F;concurrency.slide#42&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;go.dev&amp;#x2F;talks&amp;#x2F;2012&amp;#x2F;concurrency.slide#42&lt;/a&gt;</text></item></parent_chain><comment><author>mapcars</author><text>I do programming interviews and I found candidates struggling a lot in doing http request and parsing response json in Go while in Python its a breeze, what makes it particularly hard, is it lack of generics or dict data type?</text></comment>