I find this list a bit disappointing and not particularly insightful. I think that its because a lot of success is timing and luck (in addition to something be

I find this list a bit disappointing and not particularly insightful. I think that its because a lot of success is timing and luck (in addition to something being good), so it's like asking a startup founder why their startup was successful and not another. For example: - is errors on unused variables/imports really such a bold new stroke or that controversial? - is a formal spec that unusual? how many Go developers have ever looked at the spec? - was getting Docker that big of a deal other than having a good dogfooder (vs it being "killer") I agree with the open source process, kudos for them for allowing the community to help them get things right (well, some things, Go has a bunch of rough edges). IMHO, its: - Good runtime perf - Great built in libs - Built in cross-compilation and shrinkwrap binary that does not require a runtime installed on target machines - Good use of opinionated tooling (go fmt, go test, etc) that take a bunch of concerns off developers plates