Nice post! One thing though: your post is 100% feature oriented. And there’s one «feature» of Go which I don’t find here which is - in my opinion - one of its greatest strength, although it’s a non-functional one: When the design - and keep designing - the language designers were/are very careful to not introduce duplicated functionalities (i.e. they try to only provide one way to do one thing). This is why Go is simple: since there’s only one way to do things, all Go code looks pretty similar (and this is also enforced with other great Golang strengths: the tooling and gofmt)
When you work in a team, having something super consistent makes it much easier to maintain. The cognitive load when you look at the code from someone else is hardly greater than looking at your own code. When you need to develop stuff and make sure it will be developed, maintain and debugged by many developers, this very strong consistency has a huge value!