In a large company it is almost impossible to switch to a new language. You can try and convince to use some related language on some internal small project (sa

In a large company it is almost impossible to switch to a new language. You can try and convince to use some related language on some internal small project (say Scala in a Java shop). But the truth is the new language is not going to be a dramatic improvement in any area. The questions will be asked and there are no easy answers - who supports, maintains and updates it? Can we get commercial support, for how much and from who? Can we hire people? Will we able to hire in 5 years? In 10 years? Is it secure enough? How are the releases rolled out? Patches/fixes? Build processes? Code scanning? Maturity of libraries? More security questions. Can we scan the code in Fortify? Can we use AppDynamics on these apps? Do we understand its runtime well? You could probably get a few enthusiasts and build a team and get something started but the reality is it is very hard and going to take some time and the people don't tend to stick around for too long. And as a manger there is a chance you will find yourself in the middle of a large product with noone from the original team and no people excited enough to pick it up. This is why even rewrites are often a bad idea, rewrites in another language could be a business suicide for some. The truth is if we ever have a new ground-breaking programming paradigm we will not be asking the OP questions. I worked on a Scala project, it changed my thinking a bit and taught me some nice techniques, but no, I wasn't convinced enough to switch to it.