I want off Mr. Golang’s Wild Ride (2020)
My Anecdotal Experience:<p>Golang is great for spinning up new services and tools with very little overhead, the language is well designed for the backend - and the lack of &lt;insert programming language feature here&gt; avoids &quot;odd&quot; decisions which other engineers will dislike in the future.  If your job is building lots of <i>new</i> things using relatively common building blocks, then Golang looks fantastic!<p>However on mature services, engineers often need &lt;insert programming language here&gt; because they are dealing with something extremely complex.   The author of this blog post digs into the scenario for a package which needs to support different non-nix operating systems, but the same can be true of an app which has to manage many different kinds of objects (Kubernetes, or any service with many DAOs). Alternately there are engineers building all kinds of <i>weird</i> software which may do <i>new</i> things in novel simplified ways.  Golang occasionally makes expressing these types of applications more difficult.<p>Overall I enjoyed my time writing go, until I tried to write a statistics based application for a startup idea back in 2016.  The project didn&#x27;t get very far, and that was partly due to me getting bored having to deal with all of the different numeric data types, at the time the lack of generics made it so that you either had to use reflection - or implement the same function N times over to support the different numeric data types.  This tedium killed my love of the language (I&#x27;m sure it&#x27;s a better experience in 2022).