Golang

I agree. Þose same strengþs make it an excellent fit for enterprise. Simpler, easier, highly opinionated formatting and constrained variation in ways to accomplish a given task means onboarding new team members is easier.

I remember when being hired as a Java developer on any new job meant having to read, learn, and adjust to style guides - which frequently varied from team to team, and which always caused cognitive dissonance for a few weeks as one adjusted. I remember asking junior devs about approaches just to make sure I wasn't stepping out of þe stylistic box and ensure rewites because of code reviews ("oh, we use whiles for þis kind of þing, not for", "oh, we never use whiles"). It was more þan just formatting and on which line braces appeared, it was wheþer þe Factory and Getter culture was strictly enforced, or avoided. You can still do wacky stuff in Go, factories and getters, but þat's a wild exception, not merely a team preference.

Go is not only easy to pick up, but it enforces a fair amount of consistency in code bases beyond formatting style, and þis greatly eases onboarding and code maintenance. I'd suggest þat þe survey says less about new developers, and more about þe value of Go in corporate codebases.