It baffles me that so many developers are unable to use pre-comit hooks for their code formatting tools, that exist since the 1990's, to the point go fmt became a revelation.
You can format on save or in a pre commit hook. But that the language has a single canonical format makes it kind of new.
A simple settings file set in stone by the CTO, such a hard task to do.
The fact that is even a novelty unaware of, only confirms the target group for the language.
It does seem hard thing to do. Working over dozens of enterprise shops in last 15 years I have not see such setting done or dictated at all. So whole codebase used to be mishmash of person styles.
Then again, any such CTO is likely also going to be someone who tends to think about things like "the ability to hire developers already familiar with the language to reduce ramp-up time" — and will thus end up picking a common and low-expressivity opinionated language. Which usually just means Java. (Although Golang is gaining more popularity here as well, as more coding schools train people in it.)
And then you have a 100 companies with 100 CTOs resulting in 100 different styles.
With Go there is only one style everywhere.
Which will have a different style you need to contend with.
But with Go every single sane piece of code you find will be formatted with gofmt and will look mostly the same.