This mentions gofmt as a "what we got right" and I think that's especially worth underscoring. This seems to many language inventors and proponents like a smal

This mentions gofmt as a "what we got right" and I think that's especially worth underscoring. This seems to many language inventors and proponents like a small thing but it delivers huge value because it eliminates one common bike shedding opportunity entirely from day zero of a Go project. I've seen several newer languages embrace this, either copying it quite intentionally or just figuring hey Go has one so we should make one as well. I've seen some pretty weird formatting rules but I have very rarely seen rules I couldn't get used to, whereas I have worked on plenty of codebases without enforced formatting rules where as a result it was harder to understand the code.