Go 1.10 Release Notes
As someone with no skin in the game, it seems to me that the philosophical conundrum of Go is whether one needs to use a language designed to produce the kind of code consistency it gives to Google-scale orgs or if you&#x27;re better off working with a more &quot;dangerous&quot; or harder-to-read language which may create more technical debt but also allow you forge your own path as your devs prefer.<p>I keep looking at languages like Go and frameworks like Angular as being steered for huge-org problems, but I wonder if startups are better off incurring the debt of riskier, less conservative languages and paradigms and worrying about the technical debt only once they&#x27;ve reached the scale where it a) actually matters to your agility in delivering customer value and b) you have the capital to make it worth solving the problem.<p>Maybe this is reading too much into the generics kerfluffle, but I would love to be enlightened if anyone can clarify this further.