I find this kind of approach so limiting to a business in general. Basically you limit your choice of programming language and with that the ecosystem early on.

I find this kind of approach so limiting to a business in general. Basically you limit your choice of programming language and with that the ecosystem early on. You got 3 devs only knowing language X? OK cannot use any other language ever, because then they would have to learn something new (oh noes!). This will of course mean that additional developers also cannot apply their additional knowledge and will have to use the same language and ecosystem as the others, because they can't possibly be bothered to learn another language. Learning a new language should be a frequent thing. I don't know how many languages I have learned, but it has only ever increased my understanding of computer programming, advantages and disadvantages of approaches and it certainly has made me a better engineer. If a business does not want better engineers, sure, stick to the "we can only use what we already know!" approach. Let it take 2 weeks for people to learn a language! So what? It will pay off in the long run. You will have more experienced engineers, we have a less limited idea about computer programming and how to solve programming problems well, since they have gotten into contact with other concepts from other languages. You also get a more flexible team, that can accept building better and safer services, using the right tool for the job, instead of shoehorning everything into their only one language. You will open up more ecosystems for your whole business.