A few select quotes from Dan McKinley on choosing boring technology:
The nice thing about boringness (so constrained) is that the capabilities of these things are well understood. But more importantly, their failure modes are well understood.
Ask any dev for their best horror story at work. It will undoubtedly involve how something failed in an unexpected way.
Adding technology to your company comes with a cost. As an abstract statement this is obvious: if we’re already using Ruby, adding Python to the mix doesn’t feel sensible because the resulting complexity would outweigh Python’s marginal utility.
The question may not be, is X better than Y. Instead it might be is X better enough than Y to make up for the overhead of switching?
It’s helpful to write down exactly what it is about the current stack that makes solving the problem prohibitively expensive and difficult.
Switching between languages, tools, and stacks comes with a cost. Depending on the exact challenges and problems that cost may or may not be worth it.