Depending on the company and the projects maintaining the status quo may be the best decision you can take.
Right now we have 20 years worth of legacy code in ADA. We have a legal obligation to maintain a large percentage of that code to 2075. Our demand for programmers in this location is such that essentially we run training schools to meet demand and would have to do the same in any language.
What _possible_ advantage would there be in moving to a new language for new projects? Before the life cycle is up any new toy would be old and rusty. We have to train programmers anyway. Supporting two languages would double the overhead. Our existing skill base is productive in ADA. Real Software Engineering is only 5% programming at most.
This is of course a bit of an extreme example - but it serves to illustrate the point that in the continuum there will be plenty of companies on the 'don't move' side of the equation, where it is far more profitable to stay with what they already know, at least for now.
Right now we have 20 years worth of legacy code in ADA. We have a legal obligation to maintain a large percentage of that code to 2075. Our demand for programmers in this location is such that essentially we run training schools to meet demand and would have to do the same in any language.
What _possible_ advantage would there be in moving to a new language for new projects? Before the life cycle is up any new toy would be old and rusty. We have to train programmers anyway. Supporting two languages would double the overhead. Our existing skill base is productive in ADA. Real Software Engineering is only 5% programming at most.
This is of course a bit of an extreme example - but it serves to illustrate the point that in the continuum there will be plenty of companies on the 'don't move' side of the equation, where it is far more profitable to stay with what they already know, at least for now.