Isn't this basically the same strategy every challenger technology takes to replacing an incumbent one? The problem is your organization has to be willing to be

Isn't this basically the same strategy every challenger technology takes to replacing an incumbent one? The problem is your organization has to be willing to bet on Elm as a tool. What does the org do if you leave, get sick, or are terminated? In many ways choosing niche technologies with esoteric syntax or paradigms is like holding your organization hostage IMO. Now does that mean nobody should ever choose a new language or other tool? No, but the cost of adoption needs to be evaluated. I use Kotlin where I work right now and I had to address the same questions initially. The argument for Kotlin was that it's not that different than Java and most good Java developers can pick it up easily OR Scala developers (though they might do that begrudgingly...).