It’s also really gross how we want ultra prescriptive tools that force you to write things certain ways because we can’t trust our own coworkers to write decent code. Or learn things for that matter. I guess people don’t do code review at all?
This was tried before and it was called Java.
But there’s always an eager generation of naive programmers willing to believe the lie that this time is different.
I'm sure this depends on engineering culture, but at Google, where Go was born, there is "one way to write C++" and that is dictated by the style guide.
You have to learn many restrictions, a number of which feel arbitrary/highly subjective, and follow that. Of course, the style guide evolves over time so it's not like legacy code is consistent with new code.
The end result is that I much prefer the Go way of having fewer options in the language, instead of having those options in the language but restricting them via policy.
This was tried before and it was called Java.
But there’s always an eager generation of naive programmers willing to believe the lie that this time is different.