Proposal: Go should have generics
I work on juju (<a href="https:&#x2F;&#x2F;github.com&#x2F;juju&#x2F;juju" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;juju&#x2F;juju</a>), which all told is about 1M LOC.  In my almost 3 years on the project, I have not been bothered by lack of generics, basically at all (and I worked for 10 years in C# on projects that used a lot of generics, so it&#x27;s not like I don&#x27;t know what I&#x27;m missing).<p>Do we have 67 implementations of sort.Interface? Sure.  Is that, by any stretch of the imagination, a significantly difficult part of my job?  No.<p>Juju is a distributed application that supports running across thousands of machines on all the major clouds, on OSes including CentOS, Ubuntu, Windows, and OSX, on architectures including amd64, x86, PPC64EL, s390x... and stores data in a replicated mongoDB and uses RPC over websockets to talk between machines.<p>The difficult problems are all either intrinsic to the solution space (e.g. supporting different storage back ends for each cloud), or problems we brought on ourselves (what do you mean the unit tests have to spin up a full mongodb instance?).<p>Generics would not make our codebase significantly better, more maintainable, or easier to understand.