I wonder, did it occur to the author that problems he is talking about have nothing to do with Scala? It's about setting company standards and managing people.

I wonder, did it occur to the author that problems he is talking about have nothing to do with Scala? It's about setting company standards and managing people. Assuming that adopting more restrictive and less expressive language will solve the problem of сurbing "loose canon" developers is naive at best. The only result of such transition would be loosing good developers. Talented people are very hard to tame and that's what management is supposed to be about, not about getting bigger paychecks. So the company will eventually degrade to the very average level, where competitive advantages are hard to achieve. Of course in many cases competitive advantages are unrelated to development per se, so such transition is not necessary bad. But in what way it says anything about Scala or Go and programming in general?