I'm finding it difficult to accept the premise that generics and immutability are needed in Go.

In my case,

  var foo map[<type>]interface{}

solves 99% of issues where I would normally need generics.

The author also doesn't really specify what kind of generics, there's a huge difference between parametric polymorphism (i.e. Haskell type classes) and Java/C++/C# generics.

The sheer rapid pace of development and simplicity has made Go our primary stack.